2024-05-14 14:47:41 +02:00
|
|
|
<!-- title: About -->
|
|
|
|
|
<!-- meta_description: Read the short story behind manpageblog and why it provides a man page layout. -->
|
2024-05-20 14:11:12 +02:00
|
|
|
<!-- image_url: https://cdn.gyptazy.ch/images/boxybsd.jpg -->
|
2024-05-14 14:47:41 +02:00
|
|
|
|
|
|
|
|
<b>About</b>
|
|
|
|
|
<p>
|
|
|
|
|
Like probably the most ones I started with <i>Wordpress</i> which is a pretty cool but also a very bloated software for a personal blog.
|
|
|
|
|
Running such a software requires multiple application with different dependencies, continuous updates and more resources on the
|
|
|
|
|
system to serve the whole content. Creating additional backups of the <i>docroot</i> and the database require additional time and efforts.
|
|
|
|
|
All of this is not really necessary when the content is more or less static and comments are deactivated or not used. A flat file
|
|
|
|
|
approach provides the optional possibility to run and keep everything in git. Generated HTML pages can easily be served even on
|
|
|
|
|
low resource systems. While this way of blogging mostly targets tech-enthusiasts that are already working on Unix-like systems the
|
|
|
|
|
idea was to provide a blog engine in a layout and theming of a Unix-like `man page` (manual page). Man pages always align to the
|
|
|
|
|
same formatting based on <i>troff</i> which make man pages look always the same. While man pages provide information of a cli command
|
|
|
|
|
the idea was to adapt this to a blog. A blog also provides information and especially when serving tech related content it makes
|
|
|
|
|
much sense to provide it in a similar way. This is the story of how <i>manpageblog</i> was born.
|
|
|
|
|
</p>
|
