Set the environment variable PAGES_REPO_NWO
to a repo such as spadebuilders/EIPs
if you want to have Jekyll sites build on Netlify.
<em>(Unsupported content elided by the Agora.)</em>
<em>(Unsupported content elided by the Agora.)</em>
<em>(Unsupported content elided by the Agora.)</em>{{ post.date | date: "%Y" }}<em>(Unsupported content elided by the Agora.)</em>
<em>(Unsupported content elided by the Agora.)</em>
<em>(Unsupported content elided by the Agora.)</em>
</ul>
<em>(Unsupported content elided by the Agora.)</em>
<h2>{{ current_year }}</h2>
<ul>
<em>(Unsupported content elided by the Agora.)</em>
<em>(Unsupported content elided by the Agora.)</em>
<li><a href="{{ post.url }}" class="internal-link">{{ post.title }}</a></li>
<em>(Unsupported content elided by the Agora.)</em>
</ul>
<em>(Unsupported content elided by the Agora.)</em>
<em>(Unsupported content elided by the Agora.)</em>
<em>(Unsupported content elided by the Agora.)</em>
By Colin Garvey at [[Forestry]] https://forestry.io/blog/how-i-reduced-my-jekyll-build-time-by-61/
Using GH-flavoured CommonMark instead of kramdown
In the Gemfile
:
gem "jekyll-commonmark-ghpages"
In the _config.yml
file:
markdown: CommonMarkGhPages
commonmark:
options: ["SMART", "FOOTNOTES"]
extensions: ["strikethrough", "autolink", "table"]
plugins:
- jekyll-commonmark-ghpages
Autolink is key — means you can just past addresses and they’ll be linked automatically.
Rendering context...