This document describes the status and points to other related documentation for the www.webplatform.org “landing page” and various static content that aren’t and should not be managed by a CMS.
Static content are pages that we do not want to allow edition without audit such as: The landing page, the stewards section, the logo, and error pages. Since those pages are’t going to change frequently we could use serve plain static files directly, and when we need to change content, leverage a static site generator to create the documents but prevent us copy-pasting code through many files.
- Ensure uniformity in pages without relying on server side language
- Leverage tools to generate, concatenate, validate, minify assets before deploying; serving only static files to the live site.
- Support pages nesting in directories, for example: stewards/microsoft
- Support multiple tools (e.g. Process Markdown to HTML, Process templating engine, etc)
- Workspace has to allow contributor to use without a too steep learning-curve
- Serve as a reference to illustrate current Frontend development best-practices
User:renoirb has personally tried a few static site generators and found that DocPad was the most sensible choice. What made the choice clear was that it took less than one hour to be able to do basic things such as sub pages, and other things described in the #Requirements sections. Among the projects User:renoirb tried were: Assemble, Octopress, Jekyll, and Ghost.
Besides the fact that DocPad was uses CoffeeScript, we are not forced to use it in our own code.