Welcome to the first post “design-system-test” built by this custom Static Site Generator!

This generator is designed for maximum performance and minimal overhead.

This post serves as a comprehensive test case for all the Markdown features our SSG needs to support. This includes standard formatting like italics, bold text, and even strikethrough. We also require full support for links to external resources, such as the official Go documentation.

Quotes, Footnotes, Typography

Blockquotes (Quotes)

This is a critical feature for referencing sources and philosophical statements:

“Make simple things easy and hard things possible.”

— Rich Hickey (on programming language design)

Sidenote & Footnotes

We are testing the footnotes feature, which will eventually be rendered as a sidenote on the right side of the page. This is a crucial feature for adding contextual commentary without disrupting the main text flow1. This feature helps keep the main argument clear and provides further reading or context in a visually appealing way2.

Typgraphy Test

This markdown

Will the "quotes" get replaced correctly - n-dashes as well -- even m-dashes---not that I would use those?
What about 'single quotes'? What's an apostrophe? Don't forget ellipsis ...

renders to:

Will the “quotes” get replaced correctly - n-dashes as well – even m-dashes—not that I would use those?

What about ‘single quotes’? What’s an apostrophe? Don’t forget ellipsis …

Ligatures

Standard f-ligatures:

  • ⟨f‌i⟩ fi ⟨f‌i⟩ fi
  • ⟨f‌l⟩ fl ⟨f‌l⟩ fl
  • ⟨f‌fi⟩ ffi ⟨f‌fi⟩ ffi
  • ⟨f‌fl⟩ ffl ⟨f‌fl⟩ ffl
  • ⟨f‌j⟩ fj ⟨f‌j⟩ fj
  • ⟨f‌f⟩ ff ⟨f‌f⟩ ff

h4 Heading

text

h4 Heading

text

We don’t want to use h5
or worse h6

Images and Media Assets

The path below is a local reference that your Go program will need to detect and rewrite to a Cloudflare CDN URL.

Observe how the figure scales with different screen widths.

Figure:

Fig. 1: A placeholder image with a Canon SLR (Laurens Neinders on Unsplash)
Fig. 1: A placeholder image with a Canon SLR (Laurens Neinders on Unsplash)

Code Blocks and Syntax Highlighting

As a developer blog, code presentation is essential. We use fenced code blocks with language identifiers for accurate syntax highlighting (implement using chroma).

package main

import (
    "fmt"
    "time"
)

func main() {
    // A simple demonstration of Go concurrency
    fmt.Println("Starting SSG build...")
    
    go func() {
        time.Sleep(1 * time.Second)
        fmt.Println("Finished file processing.")
    }()

    fmt.Println("Main thread completed.")
}

A python one:

def hello() -> str:
    return "hello"

print(f"output: {hello()}")

The same listing without py annotation:

def hello() -> str:
    return "hello"

print(f"output: {hello()}")

Lists

We support both unordered and ordered lists:

  1. First item in the ordered list.
  2. Second item, which contains a nested list:
    • Sub-item A.
    • Sub-item B.
  3. Third item.

Conclusion

This file confirms our SSG can handle YAML front matter, footnotes, and blockquotes.


  1. This is the primary sidenote content. It often contains citations, extended definitions, or tangential thoughts. ↩︎

  2. Here is a second, slightly longer sidenote to test how the layout handles multiple sequential margin notes. ↩︎