Sitetool

DESCRIPTION

Sitetool is an extendable CMS that should aid developers building their projects web-sites without having to write HTML directly (or via strange machineries) while having a "programming" approach to the generation of their contents.

Sitetool site/contents generation is divided in two layers: backend and frontends.

In order to to transform the frontend output to the common SXML format a chain of filters get computed automatically. Filters chains are automatically formed using FCP.

USAGE

Filters

A filter is nothing more than a program which takes an input file and traslates it to an output file, usually in a different format. Sitetool comes with a set of filters:

Filter chains examples:

In order to use third-party filters or your own filters, the sitetool-config script should be used to find the filters installation directory:

Usage: sitetool-config [OPTIONS]

OPTIONS:
    [-h|--help]
    [--version]
    [--filters-dir]
    [--styles-dir]

To use external filters ... simply copy them into the filters directory.

Use

Sitetool is composed by a bunch of utilities. Each utility could be invoked manually or by using the main program sitetool via the --mode option. The main program invocation has the advantage of handling the inter-utility dependencies automatically.

The complete input grammar is available.

Current available modes are:

COPYING

The project is licensed under the GNU General Public License, version 2

MAINTAINERS

Francesco Salvestrini

AUTHORS

Francesco Salvestrini

Alessandro Massignan

MAILING LISTS

The project has a single moderated mailing list, with an archive. In order to post a message to the mailing list you must be subscribed. Please consult the mailing list page for more information on subscribing to the mailing list.

REPORT A BUG

If you think you have found a bug then please send as complete a report as possible to <sitetool-generic@nongnu.org>. An easy way to collect all the required information, such as platform and compiler, is to include in your report the config.log file available at the end of the configuration procedure.

If you have a patch for a bug that hasn't yet been fixed in the latest repository sources, please be so kind to create it using the repository sources, not the release sources.