Markata Changelog


wikilinks are now enabled by default ex: [[home-page]]. This will create a link <a class="wikilink" href="/home-page/">home-page</a>. This will automagically just work if you leave markata.plugins.flat_slug plugin enabled (which is by default).

ProTip: this was highly inspired by the marksman-lsp by artempyanykh which can autocomplete post links in this style for you.





new cli command

More information in the base_cli-docs.

# create a new blog template
# copier requires you to specify a directory
markata new blog [directory]

# create a new blog post
markata new post

# create a new plugin
markata new plugin

markata new --help

 Usage: markata new [OPTIONS] COMMAND [ARGS]...

 create new things from templates

╭─ Options ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ --help          Show this message and exit.                                                                                                                                       │
╭─ Commands ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ blog       Create a new blog from using the template from                                                                   │
│ plugin     Create a new plugin using the template at                                                                     │
│ post       Create new blog post in the pages directory from the template at                                               │

sluggify paths

python-sluggify was implemented to ensure good urls are in place despite the name of the original file.

For examples of how python-slugify will change your url's see the project's home page. One difference is that markata will leave /'s for routing in the slugs.


If you have an existing site and do not want to implement redirects or if you do not want to use slugify, you can opt out by setting slugify=False in your markata.toml.


Migrating to slugify

From the command line with markata>=0.5.0 installed run the migration script from the command line to create a redirects file in the default location. This should avoid all 404's as it will create a redirects file that many static hosting providers will issue a server-side 301 for, and for those that don't, markata.plugins.redirects creates a redirect html page, that will kick in as a backup.

python -m markata.scripts.migrate_to_slugify

configurable page template

Now injects seo into the default template through configuration. Here is an example, by adding this to your markata.toml configuration.

name = "og:type"
content = "article"

name = "og:author"
content = "Waylon Walker"

name = "og:site_name"
content = "Waylon Walker"

name = "theme-color"

name = "twitter:creator"

You will end up with these meta tags in your html.

<meta name="og:type" content="article" />
<meta name="og:author" content="Waylon Walker" />
<meta name="og:site_name" content="Waylon Walker" />
<meta name="theme-color" content="#322D39" />
<meta name="twitter:creator" content="@_waylonwalker" />

You can have an array of toml tables with a key of text. The text will be added as plain text to the end of the head of each page.

text = """
img {
width: 100%;
height: auto;
ul {
  display: flex;
  flex-wrap: wrap;

li {
  flex: 1 2 400px;


Descriptions will now properly end up in each page.

<meta name="description" content="Fix: article Fix: service worker is not upating client without hard refresh 0.6.0.dev2 Feat: create teardown lifecycle method 0.6.0.dev3 #110 Fix: implement tea" />

Config Overrides

Each post can override config settings such as head. New meta tags can be added to a single post, or anything that your template might reference from config.

      - content: waylonwalker
        name: author
      - content: "@_waylonwalker"
        name: "twitter:creator"
      - href:
        rel: canonical
      - value: <link rel='stylesheet' href='/my-extra-styles.css' />

ipython extension

Markata has an ipython extension if you want ipython to automatically load with an instance of Markata mapped to m and markata you can add the following to your ~/.ipython/profile_default/



To keep existing behavior add this to your markata.toml.



Double Runs

Previously markata would catch AttributeError and run the previous step any time you ran a step too early. The way this was implemented caused some steps such as pre-render and post-render to run twice with every single run.

This change will no longer catch attribute errors. If you run into any issues with your plugins not running before asking for attributes created by your plugin make sure that you implement the @register_attr decorator.


prettify html has been turned off by default as beautifulsoup4 prettify was taking a significant time, and was often popping up as the slowest parts in my personal _profile. If you want to continue running prettify throughout the build you can set a flag in your config to continue running prettify.

prettify_html = true


Skipped from a bump2version misconfiguration.


breaking change to feeds config

If you are using the 0.1.0 version of feeds, and have configured custom templates in markata.feeds.template and markata.feeds.card_template they will need to be moved to markata.feeds_config.

Here is what you need to do to update your feeds_config.

+ [markata.feeds_config]
+ template="pages/templates/archive_template.html"
+ card_template="plugins/feed_card_template.html"
- [markata.feeds]
- template="pages/templates/archive_template.html"
- card_template="plugins/feed_card_template.html"

markata.feeds will only be used to configure feeds pages.

map entire posts

post is now exposed to the object, allowing you to return a list of posts.

m = Markata()
# 'post' will return the entire post'post', filter='"git" in tags')

Customizable colors

# default dark theme
color_bg = '#1f2022'
color_bg_code = '#1f2022'
color_text = '#eefbfe'
color_link = '#47cbff'
color_accent = '#e1bd00c9'
overlay_brightness = '.85'

# pink and purple
color_bg = 'deeppink'
color_bg_code = 'rebeccapurple'
color_text = 'white'
color_link = 'aqua'
color_accent = 'peachpuff'
overlay_brightness = '1.2'

# default light theme
color_bg_light = '#eefbfe'
color_bg_code_light = '#eefbfe'
color_text_light = '#1f2022'
color_link_light = '#47cbff'
color_accent_light = '#ffeb00'
overlay_brightness_light = '.95'

All New auto_description plugin

auto_description Configuration

Open up your markata.toml file and add new entries for your auto_descriptions. You can have multiple desriptions, each one will be named after the key you give it in your config.



In the above we will end up with three different descritpions, (description, long_description, and super_description) each will be the first number of characters from the document as specified in the config.

auto_descriptions are no longer duplicated

4e299d6 fixes the dedupe issue that was in develop for a while and closes #24


New cli help

After the pyinstrument plugin was fixed --version and --to-json are back, and --profile is now under the build command.


The new heading link plugin makes it easier to share the exact part of an article you want with someone, by giving clickable links to the id of the heading it's next to.



Initial Release 🎉