Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>For pure HTML, you could go down the route of using a <code>static site generator</code>. For example:</p> <ul> <li><a href="http://jekyllrb.com/" rel="nofollow"><strong>Jekyll</strong></a></li> <li><a href="http://docs.getpelican.com/en/3.2/" rel="nofollow"><strong>Pelican</strong></a></li> </ul> <p>In Pelican you have a <code>base.html</code> template, which contains everything that you want to appear on all pages, so the header and footer etc (These can also be called <code>.header.html</code> and then referenced in the <code>main.html</code> template.</p> <p>Page content is written in Markdown, and put into folders called <code>posts</code> or <code>pages</code>, and then you run a <code>generate</code> command, and it will output all the <code>html</code> for you.</p> <p>And pages can be written like this:</p> <pre><code>{% extends "base.html" %} {% block title %}{{ page.title }}{%endblock%} {% block content %} &lt;h1&gt;{{ page.title }}&lt;/h1&gt; {% import 'translations.html' as translations with context %} {{ translations.translations_for(page) }} {{ page.content }} {% endblock %} </code></pre> <p>So it extends the <code>base.html</code> template. </p> <p><strong>Further reading:</strong></p> <ul> <li><p><a href="http://fjavieralba.com/pelican-a-static-blog-generator-for-pythonistas.html" rel="nofollow">Pelican: a static blog generator for Pythonistas</a></p></li> <li><p><a href="http://docs.getpelican.com/en/3.1.1/getting_started.html" rel="nofollow">Pelican - Getting started</a></p></li> </ul>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload