Yes, I get your point re: AsciiDoc(tor) vs Markdown. It should not be difficult to configure Nginx to serve an HTML generated from AsciiDoc instead of the Markdown file from the referenced URL. In this case, the ADOC files would end up in the dream.public.cat.git repository. We simply need to figure out a way to build them from source and output the wanted HTML at the right URLs. It should be straightforward. My plan last week was to include the nginx.conf anyway into this repository.
I propose that in the meantime you keep working on AsciiDoc documents until we set up a proper publishing workflow, and reference those files from the first post, so we can publish the links already – they will be indexed in search engine early, so that they’ll gain SEO over time. Once we have the final versions, we can simply switch to the HTML files (since nginx will serve static files in priority, skipping hitting the proxy for dynamic content).
Should we include the 6kly-cycles image in the web site somewhere?