Tags:
create new tag
, view all tags
The default webs for the DevelopBranch are in subversion, see http://svn.twiki.org/svn/twiki/branches/DEVELOP/data/

They were imported - with full RCS history as commited through TWiki to TWiki.org - from r1821 and culminating at r3169 - a while back.


To simplify the structure I am going to change the Webs in DevelopBranch to be

  • Users - all registered Users and Groups
    • Read-Only, with each user having write access to their topic (and no create permissions) - though somehting needs to be allowed for GroupCreation
  • Documentation - initially all the doccumentation, but we should consider seperating out User, Admin and Install Documentation
    • This web should be able to be deployed in Read-Only mode
  • Configuration - contains all the topic that allow the Administrator to configure
  • Templates - contains all the template topics that are used to create topics (Form and Topic Templates)
    • i'm not sure about this ...
  • TestCases - smile
  • _default

My expectation is that the first thing that happens after an install has happened is that we direct the administrator to create & select a default Web.

I think that the Configuration Web should be a simple UI that is intended more for an experienced TWikiAdmin, with links to the appropriate Documentation Topics.

importantly, I will have to work on the UpgradeTWiki script to allow easy but optional migration from the old layout to the new one - though i'm really targetting new installations more than existing ones.

It will / would be better if we had nested Webs, that way we would get TWiki.Documentation.TWikiVariables and TWiki.Configuration.ManagingWebs etc, but that is longer term.

-- SvenDowideit - 26 Jan 2005

TestCases should not be shipped. Like TestFixturePlugin it should be trimmed from the release package.

I'm not sure about Templates either.

Bear in mind that most plugins, when unzipped, will create the TWiki web again. Given that Plugin topics are half documentation and half configuration, where should they go?

-- CrawfordCurrie - 26 Jan 2005

See my comment on the need of a "Main" web in RenameTheMainWeb.

-- RafaelAlvarez - 27 Jan 2005

Rafael, I'm not suggesting that there should not be a Main web, i'm suggesting that we should not ship one, but rather, that the creation of a user web be the first act that the new twiki installer needs to do... that way, as we don't ship it, we don't need to upgrade it either.

I have not actually done the work yet, as i realised while considering the steps, that the work would be accellerated by use of an SvnStore module smile

on the ConfigWeb - I also thing that we should have TWikiWebPreferences, UserWebPreferences and those topics in this Administrator only web

-- SvenDowideit - 05 Feb 2005

With the new config web do you intend to keep the equivalent of the Main.TWikiPreferences topic that can be used for setting site preferences but is not overwritten durring upgrades?

-- SamHasler - 05 Feb 2005

yes smile

-- SvenDowideit - 05 Feb 2005

This seems like a good time to start SplitTheTWikiWeb

-- MattWilkie - 06 Feb 2005

Edit | Attach | Watch | Print version | History: r12 < r11 < r10 < r9 < r8 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r12 - 2006-10-08 - SvenDowideit
 
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.