joesingo/mdss

A simple static site generator

mdss's Issues

Default page context in site config

Add an option default_context that is used as a base for all page contexts

Export static files

Export static files from content and template directories

Use static_filetypes site config option to determine what is a static file

Include default template(s) in package

Create a very generic base template and associated static files (css, images)

Install as package data, and change template loading to:

• look in each dir in templates_path in order
• look in package

See if there exists a way of combining loading methods in jinja. If not, create a custom loader called something like AggregateLoader that aggregates templates found via different methods

Include navigation and site index info in context

Finalise PageInfo format (add URL - anything else?)

Expose breadcrumbs and list of child pages in PageInfo format

Also expose a recursive listing that includes children of children etc

Find content in same dir as mdss_config.yml by default

If content is left unset, default to the same directory that mdss_config.yml was found in

Implement draft mode where changes are automatically reloaded

Watch content and template dirs for for changes

Re-export site to a temporary directory

Use built into http server to serve

Include external yaml file in context

To allow re-use of context variables on different pages, allow a YAML file to be included.

Re-using variables was useful for maths notes -- can specify extra stylesheets, js for MathJax in one place and re-use on each page

Consider adding current page PageInfo to top level template context

as a shortcut to breadcrumbs[-1]

Raise error if no pages are found in content dir

Specify sort order of child pages

i.e. to override existing alphabetical ordering

Search up directory tree for site config

Similar to how finds .git directory

Also give option to give path to site config

Don't show python traceback for expected errors

e.g. raising invalid page error, no content error etc.

Instead create MdssException base exception that others can inherit from -- then wrap command line script as

try:
    # stuff
except MdssException as ex:
    parser.error(ex)

or similar

Implement macros

Implement macros that replace

<foo arg="val">stuff</stuff>

to

foo("stuff", arg="val")

A useful built in would be to get path to static file when exported

Create example 'theme'

create and document a simple template and stylesheet in a separate repository (probably just joesingo.co.uk theme)

Document how to use external template themes in mdss readme.

this will keep core mdss and theming separated, and simplifies template loading