History of Bitweaver Framework

^''__NOTE:__ This is unofficial documentation. This page is an attempt to improve on the framework information found on ((bitweaverArchitecture)). If you are looking for official documentation, please see that pages.''^

The Bitweaver application Framework offers a complete suite of core features in a higher modular design. The Bitweaver Framework is designed specifically for developer flexibility. To understand how Bitweaver is designed, you must understand that it is completely modular, on multiple levels.

Bitweaver is made of up three main parts, the Kernel, Liberty, and Packages.
''__NOTE: confirm this characterization__''

The ((KernelPackage|Kernel)) provides a core set of global services (such as preferences, user authentication, themes, permissions, comments, content history and such) to the feature sets, aka Packages, of Bitweaver.

Liberty is ''__NOTE: add description__''

((bitweaverPackage|Bitweaver Packages)) are the largest grain of our modular architecture, they are intended to be large collections of features, such as the ((WikiPackage|Wiki Package)) or the ((BlogsPackage|Blogs Package)).

The primary goal for bitweaver was to place the __fewest possible requirements__ on a package and provide the most flexible environment possible.

This diagram uses a powertool metaphor to illustrate the functional inter-relationships of the Kernel, Liberty, and Packages:

{attachment id=125}