Static Flask sites are a big win because:
- They're fast.
- If you need your site to be dynamic in the future, the transition will be easy.
- There are well-developed extensions for doing this. Here I'll demonstrate Frozen-Flask (for building static content) and Flask-FlatPages (for writing pages in Markdown).
- L19: Tell Frozen-Flask to build the static content to the project root instead of the default
- L22: We also need to explicitly set
FREEZER_BASE_URLsince Github Pages hosts your repo pages on
- L23: Don't delete all your app files!
- L26-27: Tell FlatPages to look for
.mdfiles in the
- This is where the Flask
page(path)view retrieves a page object and passes it to the template.
project/pages/bacon.md (Page example)
- The first lines are YAML metadata. They can be accessed in views via the
page.metadict. For example,
page.meta['title']. They're also accessible in the templates, as we'll see next.
- L2: Dates are parsed by PyYAML as datetime objects.
This just imports
views so that they can be accessed without circular imports (source).
- This builds the static content to the project root.
After creating your Github repo, run the following: