bitweaverGlossary

List of bitweaver specific terms

Created by: xing, Last modification: 10 Apr 2007 (00:27 UTC) by laetzer
Administrator
Someone setting up and maintaining a Bitweaver site. This is usually also the first user in the system.
Developer
Someone to code either Bitweaver itself or addon Packages. Involved in layout as far as his one package is concerned via Smarty templates.
Feature
Packages usually contain various features that can be activated or deactivated. All these features can be set from the Administration Screen. The number of features can be daunting to begin with, but we are sure you will soon work out what they all do. most features have some short description of what you expect from the setting once turned on or off.
Group
In bitweaver groups are given permissions. You can then assign users to various groups. this makes it easy to allow a set of users to edit wiki pages but not edit blogs or vice versa.
Icon Style
Bitweaver's icons are comptatible with Gnome and KDE icon themes. Copy an appropriate set of icons to the IconStyles directory for it to appear in Administration > Themes. Appropriate means: any icon set following the Tango Desktop Project naming specs.
Layout
Bitweaver adapted Allessandro Fulciniti's Layout Gala. This gives your 40 clean, CSS-based ways how columns, header, footer, and center of your site are layed out. Design your custom Style with that basic grid in mind to take advantage of the layout control to be found in Admin > Themes.
Module
A module is one of the small boxes in one of the outer columns. You can select what modules and where you want to display these from the Layout Screen.
Package
A Package is a part of bitweaver that can manipulate, store and/or display information. Packages are always self-contained entities that can be installed, or uninstalled should require additional functionality. A list of currently available packages can be found here. bitweaver differentiates between internal and foreign packages. Internal packages are packages that have been created inhouse and are meant to work with bitweaver from the ground up and will probably not work with any other application. a Foreign Package is usually a standalone application that has been modified in a way to fit into bitweaver. We try and keep these modifications to a minimum, allowing for easy upgrades to new versions.
Plugin
"Data Plugins" give you functionality when editing pages, blogs, articels etc. They are written in curly brackets. Enable them via Administration > Liberty > Plugins. Examples: DataPluginAddtabs will join the contents from several sources in a Tabbed Interface. FLASHVIDEO displays a flash video. There are many more plugins from a simple counter, to images, MapQuest directions, RSS Feeds, Spy Text etc. You can easily write your own. An optional help panel at the bottom of editable content informs editors about data plugins currently available and how to use them properly.
Style
A Style is how an installation of bitweaver looks, like a theme or a skin. A bitweaver Style resides in the themes directory and contains a CSS file, several images, and template files. Bitweaver choses these custom templates to display your site, but falls back to standard templates if no custom file is found. Like this, it's very easy to start making your own Style of bitweaver. Custom styles can be shared on bitweaver.org for others to download, usually in the form of an archive, including a preview icon, a descripton, and screenshots.
User
When a user registers with your site, that user is added to your database. Every user has a defined set of permissions that allow them to access particular parts of your site. To manage these permissions, you have to first define groups and allocate permissions to them.

please add more terms.

Related Items

Documentation » User Documentation

Documentation written by users for users. These are generally entry level documents.

  •    •    •    •    •    •    •    •    •    •    •    •