Fork 0
Site sources and temples for slatecave.net (zola generated)
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Slatian e819b3a751 Split the ansi escape squences into their own cheatsheet 2 days ago
content Split the ansi escape squences into their own cheatsheet 2 days ago
meta Added some tagging by topic and programing language 2 days ago
static Improved table responsiveness 3 days ago
templates Added a flag that allows hiding the description that would show up as the default first paragraph 2 days ago
.gitignore Updated ssh smart jump article with some added explanations and a bit better markup 12 months ago
README.md Documented the new taxonomies and did some cleaning up 2 days ago
banners.toml Added a Brought to you by IPv6 banner 2 months ago
build.sh I like tabs, tell tidy to keep them 3 months ago
config.toml Added some tagging by topic and programing language 2 days ago
report.awk initalize warnung and error arrays in report.awk 5 months ago
robots.txt Cleanup and more SEO bots … 2 months ago


Slatians Hideout on the Interweb

This is a personal blog, projects and wiki site hosted at slatecave.net.

It is built using the zola static site generator.


Slatecave theme

The slatecave favicon


TODO: a bit more about how the theme works … in summary: semantic html with a few utility classes.


The slatecaves templating has grown quite a bit over the last year … I'll try to keep it brief.

Zola allows templates to extend another template and overwrite predefined template blocks, because of this all html templates extend base.html (which is quite a beast) and customize small parts of it.

Template Files:

Template configuration

[extra] values for sections and pages frontmatter:

  • banner string Set a custom banner for the page
  • preview_image string set a custom preview image for link previews using e.g. opengraph.
  • hide_description bool stops the description from showing up in place of a left out first paragraph.

[extra] values for sections frontmatter:

  • short_title string with a short title that is diplayed on a buttons leading to the section
  • show_feed_link bool set to true to show the feed link on the page, make sure to also set generate_feed in the general section. (There is also an or in case zola decides to expose the generate_feed option as section.generate_feed.)

[extra] values for pages:

  • pinned bool if the page is pinned it will always show up on the frontpage.

[extra] values for creation pages frontmatter:

  • creation_status string sort creation status description.
  • sourcecode_uri string the uri of the repository the project lives in.
  • fork_of string name of the project this one is a fork of.
  • fork_of_uri string uri to the project this one is a fork of.

Note: The date attribute will be displayed as the project start date.

Inline Template hints

The base.html template does some rearranging to make the section based layout with boxes possible without nightmare markdown, around h2 headlines. To mark sections as what they are one can place some inline hints about a section.

  • <!--DISCLAIMER-SECTION--> adds a disclaimer class which could be addressed by some css
  • <!--H-CARD-SECTION--> add a h-card class for use with microformats
  • <!--LANGUAGE:de--> sets lang="de" on the section to mark it as being in german.


Currently the following taxonomies are configured:

  • notebook - to place a page inside the Notebook section
    • Guides - guides and tutorials
    • Cheatsheets - Lookup tables, snippets, Cheatsheets
    • Bookmarks - A little Web directory
  • topics - What the article is about
    • Art
    • Desktop Ricing - see also screen locking
    • Electronics and Microcontroller
    • Mobile Linux - Linux on the phone
    • Networking - general, also ssh and such
    • Shell - Everything that has to do with Cli, Tui and Shellscripting
    • Tools - Expected overlap wit Shell and Web
    • Web - Everything that has to do with web technology
  • lang - Programming/Markup Language
    • Bash - see also Sh
    • C
    • Css
    • Html
    • JavaScript
    • Lua
    • Python
    • Rust
    • Sh - see also Bash, tag with both if relevant
    • Vala

Note: Html, Css and JavaScript only when it is directly about those things, otherwise place it in the topic Web.


Whenever a shortcut sourrounds something the follwoing pattern is meant:

{% shortcode() %}
*Markdown* goes [here](#)
{% end %}


Sourrounding helper for cerating definition lists, line based.

{% dl() %}
Defintion Title
: Definition Item
: Another Item
My _Website_
: [slatecave.net](https://slatecave.net)
{% end %}

Sourrounds an ordinry markdown list, adds the link-list class to any <ul> tag inside that has no attributes.

{% linklist() %}
* [Foo Site](https://example.org/foo)
* [Bar Article](https://example.org/bar)
* [Baz Code Repository](https://codeberg.org/slatian/site-source.slatecave-net)
{% end %}


Creates a link button, also known as button-paragraph to the stylesheet, which is a paragraph with exactly one link inside.

It accepts some parameters:

  • href mandatory, the destination url, if it starts with an @ zolas get_url function will be used to generate the url.
  • txt optional markdown text for the button, alternatively it may sourround the text it contains, if none of the two the button just displays its href
{% linkbutton(href="https://slatecave.net")%} Check out slatecave.net, it has linkbuttons! {% end %}


Sourround a markdown block with it to make it a HTML <figure> element.

It accepts some parameters:

  • caption an optional html string that will be inserted before the contant as <figcaption>
  • caption_after same as caption but insetrd after the figure content
{% figure(caption="Lua snippet that prints foo")%}

NOTE: this also inserted <pre> and <code> tags but they were removed in the favor of markdown proce4ssing and automatic syntax highlighting. Maybe it will be removed in the future to allow figures to be rendered in any markdown viewer.


This shortcode makes a webring widget with some fancy buttons and a frame around it.

It accepts some parameters:

  • name mandatory, the webrings name
  • headline_tag optional, defaults to p, the html tag type that shoudl be used for the headline (i.e. h2 or h3)
  • previous_uri mandatory
  • next_uri mandatory
  • random_uri optional (if the webring supports jumping to a random site)
  • search_uri optional (if the webring has a search engine)
  • about_uri optional, the link to the webrings homepage
  • about_link_text optional, custom text for the webrings homepage button