The following documentation is available about how Daizu CMS works and how to use it:
- Daizu's lack of UI
- An explanation of why Daizu, for the time being, doesn't really have a user interface.
- Development roadmap
- A plan for the stages of future development work on Daizu CMS.
- Daizu's features
- Some of the reasons why Daizu might be worth working with.
- Installation instructions
- How to install Daizu, configure it, and set up a content repository and database.
- Configuration file
- Format of the XML file used to configure each Daizu instance.
- Subversion properties
- List of properties which Daizu uses, with information about the formats of the values and how to use them.
- Command line interface
- Manual page for the
daizucommand-line interface, for maintaining working copies and publishing output. - Author metadata
- How Daizu records information about which person (or people) created particular pieces of content.
- Previewing output
- Daizu comes with a CGI script which can be used to look at a preview version of a website without publishing it.
Developer information
If you're interested in hacking on Daizu or writing plugins for it, the following will be useful. Daizu is written in Perl, so you'll need to know that in order to work on it. It uses Template Toolkit to generate pages, and the Subversion Perl API to access the content.
- Planning
- The Daizu to-do lists. Check these if you're looking for a feature which might not exist.
- Daizu Perl API
- Documentation for the Perl modules which make up the core of Daizu CMS.
- Testing
- Using the automatic tests which come with Daizu.
- Packaging
- How the source distribution is built, in a slightly unusual way.
- Release procedure
- The procedure for creating a source distribution for a new release of Daizu.
- Microformats
- Daizu's default templates support the hAtom microformat.
- Daizu repository
- How to get the latest Daizu source code from the Subversion repository.