A minimal but capable blog and Web framework that you can directly run from a Markdown folder.
This project powers the following blogs:
$ pip install madblog# The application will listen on port 8000 and it will
# serve the current folder
$ madblog
usage: madblog [-h] [--config CONFIG] [--host HOST] [--port PORT] [--debug] [dir]Recommended setup (for clear separation of content, configuration and static files):
.
-> config.yaml [recommended]
-> markdown
-> article-1.md
-> article-2.md
-> ...
-> img [recommended]
-> favicon.ico
-> icon.png
-> image-1.png
-> image-2.png
-> ...
But the application can run from any folder that contains Markdown files (including e.g. your Obsidian vault, Nextcloud Notes folder or a git clone).
See config.example.yaml for an example configuration
file, and copy it to config.yaml in your blog root directory to customize
your blog.
All the configuration options are also available as environment variables, with
the prefix MADBLOG_.
For example, the title configuration option can be set through the MADBLOG_TITLE
environment variable.
Webmentions allow other sites to notify your blog when they link to one of your
articles. Madblog exposes a Webmention endpoint and stores inbound mentions under
your content_dir.
Webmentions configuration options:
-
Enable/disable
- Config file:
enable_webmentions: true|false - Environment variable:
MADBLOG_ENABLE_WEBMENTIONS=1(enable) or0(disable)
- Config file:
-
Site link requirement
- Set
link(orMADBLOG_LINK) to the public base URL of your blog. - Incoming Webmentions are only accepted if the
targetURL domain matches the configuredlinkdomain.
- Set
-
Endpoint
- The Webmention endpoint is available at:
/webmentions.
- The Webmention endpoint is available at:
-
Storage
- Inbound Webmentions are stored as Markdown files under:
content_dir/mentions/incoming/<post-slug>/.
- Inbound Webmentions are stored as Markdown files under:
See the provided config.example.yaml file for configuration options.
The blog home page supports three view modes:
cards(default): A responsive grid of article cards with image, title, date and description.list: A compact list — each entry shows only the title, date and description.full: A scrollable, WordPress-like view with the full rendered content of each article inline.
You can set the default via config file or environment variable:
# config.yaml
view_mode: cards # or "list" or "full"export MADBLOG_VIEW_MODE=listThe view mode can also be overridden at runtime via the view query parameter:
https://myblog.example.com/?view=list
https://myblog.example.com/?view=full
Invalid values are silently ignored and fall back to the configured default.
Madblog can also render external RSS or Atom feeds directly in your blog.
Think of cases like the one where you have multiple blogs over the Web and you want to aggregate all of their content in one place. Or where you have "affiliated blogs" run by trusted friends or other people in your organization and you also want to display their content on your own blog.
Madblog provides a simple way of achieving this by including the
external_feeds section in your config file:
# config.yaml
external_feeds:
- https://friendsblog.example.com/feed.atom
- https://colleaguesblog.example.com/feed.atomFor an article to be correctly rendered, you need to start the Markdown file with the following metadata header:
[//]: # (title: Title of the article)
[//]: # (description: Short description of the content)
[//]: # (image: /img/some-header-image.png)
[//]: # (author: Author Name <https://author.me>)
[//]: # (author_photo: https://author.me/avatar.png)
[//]: # (published: 2022-01-01)Or, if you want to pass an email rather than a URL for the author:
[//]: # (author: Author Name <mailto:email@author.me>)If these metadata headers are missing, some of them can be inferred from the file itself:
titleis either the first main heading or the file namepublishedis the creation date of the fileauthoris inferred from the configuredauthorandauthor_email
You can organize Markdown files in folders. If multiple folders are present, pages on the home will be grouped by folders.
Images are stored under img. You can reference them in your articles through the following syntax:
You can also drop your favicon.ico under this folder.
LaTeX support is built-in as long as you have the latex executable installed on your server.
Syntax for inline LaTeX:
And we can therefore prove that \( c^2 = a^2 + b^2 \)Syntax for LaTeX expression on a new line:
$$
c^2 = a^2 + b^2
$$Feeds for the blog are provided under the /feed.<type> URL, with type one of atom or rss (e.g. /feed.atom or
/feed.rss).
By default, the whole HTML-rendered content of an article is returned under the entry content.
If you only want to include the short description of an article in the feed, use /feed.<type>?short instead.
You can also specify the ?limit=n parameter to limit the number of entries returned in the feed.
For backwards compatibility, /rss is still available as a shortcut to /feed.rss.
If you want the short feed (i.e. without the fully rendered article as a
description) to be always returned, then you can specify short_feed=true in
your configuration.