print page  |  view normal version 

Section 1.2 - Design principles

Enano's design model is similar to that of most wiki engines: it uses namespaces and a more or less standardized formatting scheme. A namespace is a group of pages that share a common function or purpose. Every namespace except Article has a short string of text prepended to its URL. There are several namespaces that are part of the Enano core:

  • Article: the "main" namespace. The name "Article" is only used internally. Most pages stored in the database will go in this namespace.
  • User: the namespace used for "user pages", or personal pages that users can create. By default, a user is granted permission to edit his or her user page upon registration.
  • File: Used for files uploaded through Enano's interface. File pages show a normal Enano page, but with a box on the bottom that shows information about the file and any past revisions of it.
  • Help: Currently identical to the Article namespace except for the first tab under the page toolbar, which is labeled "documentation page" instead of "article." This namespace is recommended for use with documentation-related pages.
  • System: Stores "system messages", or messages that Enano templates can fetch on demand. The prefix for this namespace is "Enano:" by default.
  • Template: Used for "templates" or pages whose contents can be embedded into other pages. The navigation box at the bottom of this page uses a template.
  • Category: Used for listing out pages in a category. Categories are identical to regular Enano pages, except that they show a box on the page listing all member pages.
  • Project: Currently identical to the Article namespace except for the first tab under the page toolbar, which is labeled "project page" instead of "article." You should use this namespace for pages that are specific to the technical aspects of your site. For example, the GFDL page on this site houses a copy of the GNU Free Documentation license.
  • Special: Exactly as it says. Special pages aren't stored in the database - rather, they are created at run-time by plug-ins. Special pages consist of a custom function that is run when the page in question is requested.
  • Admin: Identical to Special, except that Admin pages don't need to be registered via the Enano API - just create the function and request the page.
Previous Section 1.2 - Design principles Next
Concept, vision, and history Up one level Installing Enano on your server
© 2007 Contributors. All content is under the GNU Free Documentation License.
Powered by Enano | Valid XHTML 1.1 | Valid CSS | Time: 0.04s