Bureaucrats, checkuser, Interface administrators, interwiki, Administrators (Semantic MediaWiki), Curators (Semantic MediaWiki), Editors (Semantic MediaWiki), staff, Suppressors, Administrators
83,693
edits
Category:Bitweaver: Difference between revisions
m
→Contents of Bitweaver: Template:Clarify
Hoof Hearted (talk | contribs) (woot woot - release 4 is available!) |
Hoof Hearted (talk | contribs) |
||
| Line 36: | Line 36: | ||
Being derived from the feature rich code base of its progenitor, [[:Category:TikiWiki|TikiWiki]], the primary challenges were to remove the lesser-used software features from [[TikiWiki]]. After completely modularising the code base, the main features (known as 'packages' in Bitweaver) were updated, and new capabilities were added. During this process of modularising and code rewriting, the authors of Bitweaver decided to introduce a centralised content management package called [http://www.Bitweaver.org/wikiLibertyPackage liberty]. This means that almost all content is stored in a common location, making new package development very easy, and providing a common standard across the entire platform. | Being derived from the feature rich code base of its progenitor, [[:Category:TikiWiki|TikiWiki]], the primary challenges were to remove the lesser-used software features from [[TikiWiki]]. After completely modularising the code base, the main features (known as 'packages' in Bitweaver) were updated, and new capabilities were added. During this process of modularising and code rewriting, the authors of Bitweaver decided to introduce a centralised content management package called [http://www.Bitweaver.org/wikiLibertyPackage liberty]. This means that almost all content is stored in a common location, making new package development very easy, and providing a common standard across the entire platform. | ||
This architectural design has made it is possible to work with a set of pristine files (e.g., downloaded and kept up to date using {{tag|CVS}}), | This architectural design has made it is possible to work with a set of pristine files (e.g., downloaded and kept up to date using {{tag|CVS}}),{{clarify}} and drop in custom packages to add any functionality required for a particular point installation. In addition, unused packages can be removed simply by deleting the package directory from the server, thus making Bitweaver as compact or as comprehensive as desired. | ||
==Activity== | ==Activity== | ||