Of course every blog needs images. After all a picture is worth a 1,000 words. I'm giving this a shot hosting the images in the GitHub repo. That will work for now.

With any luck there is a nice picture right above this line.

I discovered I needed to add the images directory under assets so that it gets picked up correctly and the path to /assets/images must be absolute.

Here's what my local AI told me about YAML front matter:

You can include almost any piece of metadata that helps define, categorize, or guide how your content should be displayed or processed by the system reading it (like a static site generator).

Since the function of the front matter is to act as structured data *about* the content rather than the content itself, you can think of it as adding YAML key-value pairs for anything non-narrative.

Here is a comprehensive list of common things you might include:

### 1. Publishing & Timing
These control when and how often the content appears chronologically.

*   **`date:`**: The original creation or publication date (most common).
*   **`pubdate:` / `published:`**: A specific date intended for public viewing, which might be different from the file's actual modification date.
*   **`last_modified:`**: When the content was last substantially edited.

### 2. Categorization & Indexing
These help navigation and filtering on your site.

*   **`tags:`**: A list of keywords (e.g., `["python", "api", "testing"]`).
*   **`categories:`**: Broader groupings, often mutually exclusive to tags (e.g., `"Programming"`).
*   **`series:`**: To link posts that belong to a multi-part tutorial or series.

### 3. SEO & Display Control (For Web Presentation)
These guide search engines and the site's rendering logic.

*   **`slug:`**: A clean, URL-friendly version of the title, often mandatory for creating permalinks (e.g., `my-awesome-post`).
*   **`excerpt:` / `summary:`**: A short summary that should be displayed on an index page without reading the whole article.
*   **`featured_image:`**: To specify a path to an image that should represent the post on index pages.
*   **`canonical:`**: Used for SEO to point search engines to the primary version of a page if multiple URLs exist.

### 4. Per-System Directives (Site Generator Specific)
Some generators have proprietary keys you *must* use to make specific features work:

*   **`layout:`**: Tells the site generator which template file to use for rendering this specific post (e.g., `layout: "video_post"`).
*   **`draft:`**: A boolean flag (`true`/`false`) used to keep posts private until they are ready to go live.
*   **`math_engine:`**: Specific directives needed by LaTeX/MathJax implementations if you embed math equations using specific syntax.

By adding these kinds of structured keys, you turn a simple Markdown file into a self-contained data object that your website software can read and use to build out a complex, functional website.

Mostly I'm interested in getting the dates right so I can add tehm to the posts.

This would be pretty handy, if it works.

Looks like the naming scheme is setup to chain multiple posts on the same day together. That's fine, but I'll need to keep that in mind as I work through things.

I'm going to try some variations to see if it's always true, it if I can get more granular.

This blog is created using PHP, Sculpin, Git, and Github Pages.

namespace Foo;

/**
 * Awesome Contrived Example.
 */
class Bar implements BarInterface
{
    private $baz;

    public function __construct(BazInterface $baz)
    {
        $this->baz = $baz;
    }

    public function doIt()
    {
        return $this->baz->do('it');
    }
}

You can also use fenced code blocks with a syntax declaration at the top. You can use either ~ or ` to mark them.

if ($fencedCodeBlock->syntax !== 'PHP') {
    throw new UnexpectedValueException("wat");
}

Like this addition to the skeleton? You can thank for @Pawka for suggesting it. :)

Ut in mauris augue, vitae facilisis purus. Nam ullamcorper pharetra lorem, cursus lobortis tellus facilisis congue. Etiam ac dapibus lectus. Nunc tempus ullamcorper felis, eu sagittis risus mollis aliquam. Mauris congue orci ac metus egestas porta nec ac lectus. Nam ac neque vitae quam sagittis dapibus. Morbi sit amet erat ac justo rutrum molestie id in tortor. Proin egestas tortor neque, eget fringilla nunc. Donec consequat purus ac risus dignissim dignissim. Praesent dui nisl, suscipit sed cursus in, dictum non elit. Nulla eget congue nisl.

Morbi hendrerit porta ante, dapibus adipiscing nibh ornare at. Nullam iaculis porta ante, at semper tellus auctor nec. Vestibulum nec justo sed purus elementum venenatis. In hac habitasse platea dictumst. Fusce nibh tellus, varius non commodo sit amet, eleifend placerat nisl. Donec sit amet enim cursus ligula adipiscing auctor. Nullam sagittis porta ligula vitae rutrum. Aenean id sapien mi, elementum ullamcorper lectus. Aliquam erat volutpat. Fusce bibendum, leo ultricies lacinia viverra, mauris urna fermentum sem, id tempus lectus nunc faucibus magna. Vestibulum risus mi, tempus ut lobortis non, mattis sed diam. Nunc at mattis leo.

Ut erat nunc, vestibulum sit amet sodales non, tincidunt nec justo. Integer vitae tortor massa. Vestibulum tincidunt commodo lacus, ac cursus lorem mattis eu. Donec ut magna vel urna fermentum congue. Donec laoreet neque at velit imperdiet luctus. In consectetur lacus eu purus dictum a imperdiet leo ullamcorper. Phasellus consequat feugiat tincidunt. Quisque vel orci in mauris fermentum pretium.

Pellentesque rhoncus accumsan auctor. Nunc venenatis tellus non ante pharetra pretium. Sed rutrum, eros eu tristique luctus, neque sapien ultrices felis, id varius orci erat eget leo. Curabitur ut volutpat diam. Phasellus porta neque vitae nisi sodales ultrices. Etiam ultricies blandit lorem, id accumsan eros facilisis vel. Praesent nulla sapien, laoreet sit amet dapibus sit amet, tincidunt vitae neque. Vestibulum aliquam sollicitudin urna, in facilisis dui aliquam id.

In honor of this milestone, this post is written in Textile.