Examples

• Server generated page - (pug)
• Server generated stylesheet - (stylus)
• Server generated script - (coffee-script)

Also see browser JavaScript console for proof of concept. Extensions are mapped to one handler, no content negotiation. Also paths with extensions may be forcefully redirected to the published variants.

The current implementation maps a path extension to an Express handler. There is little in the sense of true resources yet, the content is served with the local path without extension as the URL. No negotiation, and most routers are rather primitive and don't do much with headers or a lot of input sanitizing and error handling.

• This is a markdown file

• The ReadMe is formatted in Docutils reStructuredText

• The media/, public/components/ and example/ directories are served directly from filesystem paths using the static router. The static router does not create indices, but redirects to the 'index' or 'main' files if present.

• Sh - (script)

Paremeterization

Routers can inspect the entire application context.

The resource context is initialized with a 'route.options' attribute to hold any custom data. The data is loaded from the Sitefile if given.

Router modules have an defaults attribute, this can also provide default 'route.options'.

Query to handler options

Graphviz

From Graphviz dotguide

• Back to ReadMe