Testing the Static North Publishing Flow

The goal

The goal is to prove that adding an article is mostly a writing task. There is no database record, route registry, or admin screen to update.

This single MDX file provides:

• the article metadata shown around the page
• the text included in search
• the headings used by the table of contents
• the tags and category archive links
• the article URL

Frontmatter controls the listing

The block between the two --- markers is called frontmatter. Static North reads it automatically when it discovers this file.

title: "Testing the Static North Publishing Flow"
category: "Static North"
tags:
  - MDX
  - Authoring
draft: false

Markdown handles most content

Ordinary Markdown is enough for paragraphs, emphasis, lists, links, tables, and code. Inline commands such as npm run dev receive technical styling automatically.

Code blocks are enhanced automatically

Adding a language after the opening backticks enables syntax highlighting. The article layout also adds the copy button.

type TestResult = {
  articleFound: boolean;
  route: string;
};
 
const result: TestResult = {
  articleFound: true,
  route: '/fixes/test-article',
};
 
console.log(result);

A reusable command component

MDX also allows the small set of components documented in the README:

Once the development server is running, open this test article and try searching for “authoring” or “publishing flow.”

What to try next

1. Change the title and save the file.
2. Add another heading and watch it appear in the table of contents.
3. Add a new tag and follow its generated tag link.
4. Copy this file into another content directory to create a different content type.