Why: the goal or problem

A text-first publishing team needs reusable layouts and predictable builds. Rewriting complete pages for each post wastes effort.

How: work toward a solution

Start with three Markdown articles and one layout. Next runs the Ruby build, creates an index and three article pages, then sends files through hosting to the browser. Missing layout stops this example before output. Reading these files needs no Ruby request handler. Personal Save records need a separate API. Previous, Reset, or reload restores earlier states.

Jekyll: concept simulation

Concept simulation

Jekyll

Next traces source → build → output → host → browser.

Build environment ends before hosting

  1. 01 Three Markdown articles + layout
    • A17.md
    • B04.md
    • C99.md
    • Shared layout
  2. 02 Ruby build · layouts

    Waiting

  3. 03 Generated HTML files 0

    index.html · A17.html · B04.html · C99.html

  4. 04 Static host · publish files
  5. 05 Browser · read three articles

Three Markdown articles + layout

A fictional demo within this article. Reset or reload restores its initial state.

What: the concept

Jekyll transforms Markdown and layouts into a static site using a Ruby build workflow. Generation and hosting are separate choices.

Maintain build dependencies separately from hosting.

Source