<feed xmlns='http://www.w3.org/2005/Atom'>
<title>infrastructure/haunt-blog/posts/2017_12_contributions-to-arcep-work-on-terminal-devices-and-public-consultation.md, branch main</title>
<subtitle>Work to migrate blog.replicant.us from WordPress to a static and flexible website generator.
</subtitle>
<link rel='alternate' type='text/html' href='https://git.replicant.us/contrib/GNUtoo/infrastructure/haunt-blog/'/>
<entry>
<title>Move blog posts to the posts/ directory.</title>
<updated>2025-06-14T23:30:32+00:00</updated>
<author>
<name>Denis 'GNUtoo' Carikli</name>
<email>GNUtoo@cyberdimension.org</email>
</author>
<published>2025-05-03T10:38:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.replicant.us/contrib/GNUtoo/infrastructure/haunt-blog/commit/?id=83d796eeb1c8db91b8a11f36eb00f91bce8173e0'/>
<id>83d796eeb1c8db91b8a11f36eb00f91bce8173e0</id>
<content type='text'>
We also have two other pages that are not generated from the blog posts
(reply.html and search.html).

It would be nice to be able to move them to markdown as well, but if we do
that it is necessary to differenciate between markdown files used to generate
blog posts, and the ones used to generate these pages.

In addition if the blog posts directory is named markdown, and that we have
other markdown files as well, it become confusing for contributors.

Signed-off-by: Denis 'GNUtoo' Carikli &lt;GNUtoo@cyberdimension.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
We also have two other pages that are not generated from the blog posts
(reply.html and search.html).

It would be nice to be able to move them to markdown as well, but if we do
that it is necessary to differenciate between markdown files used to generate
blog posts, and the ones used to generate these pages.

In addition if the blog posts directory is named markdown, and that we have
other markdown files as well, it become confusing for contributors.

Signed-off-by: Denis 'GNUtoo' Carikli &lt;GNUtoo@cyberdimension.org&gt;
</pre>
</div>
</content>
</entry>
</feed>
