Render+cache for static pages hosted elsewhere

[abitrolly]

It is useless double effort to maintain the same content in custom UI of hackerspace.by website for registered members and on GitHub for the rest of hacker community. The effective way to handle this is to render and cache pages from GitHub and provide a link to repository.

The rationale is that skills and practice to use GitHub is more beneficial for people than skills to use Keepass and web forms.

[abitrolly]

The plan to create a Jekyll style git publishing with Ruby on Rails.

1. Create _content dir for markdown posts. Inspired by Hugo, but uses _ prefix like Jekyll. The _ is needed to separate content from Ruby application files.

2. _content lookup will be made after standard lookup for URL handler fails. For example, request to https://hackerspace.by/projects/malinohs will get the _content/projects/malinohs.md and will render it in standard site layout with a reference that this page can be edited on GitHub.

The markdown processor should understand data blocks from Hugo/Jekyll markdown files.