Conventions

The following conventions govern my Homepage.

Terminology

The Homepage system uses these terms consistently:

Roles

The Homepage anticipates these roles:

  • : The person maintaining the system

  • : The person maintaining the Content

  • : The person visiting the Frontend

Chrome

The user interface has this structure:

  • : The Frontend as it is used by the individual User

  • : The main area in which the actual content is shown

  • : A panel for the User to manage Client settings

  • : The adaptive navigation path at the top-left of the Frontend

  • : The static legal links at the bottom-left of the Frontend

  • : A piece of Frontend UI originating from rendered Markdown

  • : A piece of Frontend UI rendered from a purposed code block

  • : A frontmatter value deciding the visibility of a content

Pages

Pages are the website-native format:

  • : A collection of standalone *Page*s

  • : A focussed Pages content, eventually nested

Posts

Posts are a Blog specific format:

  • : An collection of chronologic *Post*s

  • : A focussed Blog content.

Presentations

Presentations are a Powerpoint-like format:

  • : A collection of *Chapter*s and *Slide*s

  • : A generated first slide that starts the Presentation

  • : A generated second slide listing all Chapters contained

  • : A collection of Slide*s and their first *Slide

  • : A focussed Presentation content

Status

These frontmatter Status flags decide a content's visibility:

Archived

Retained, but excluded from active output.

Use if you want to remove that content from everywhere except the filesystem.

Draft

Work in progress.

Use when the content is not yet ready to be published, but on it's way.

Hidden

Generated, but not listed by default.

Use when a content should only be accessible if it's URL is entered directly.

Published

Normal live/listable content.

Use when the content is alive and well and everybody should see it.

Collapsibles

Some content is collapsible: Expandables, Tables, Code blocks, and Lists, as well as sections in Blog Posts and Pages.

Consecutive collapsible Code blocks, Expandables, and Tables share one group across kinds when their responsive-width conditions match. Blank lines and ordinary comments do not split the group. Put the exact comment on its own line outside a fenced code block to start a new group at the next Element. The marker stays invisible. exclusivity applies across the shared group. Foldable sections and nested list-item toggles remain separate.

Closed

A collapsible can be closed by default, using .

Example

  • Hello

  • World

Markdown
Example [v]
  - Hello
  - World
Opened

A collapsible can be opened by default, using .

Example

  • Hello

  • World

Markdown
Example [<]
  - Hello
  - World
Grouped

A collapsible can be grouped, using any syntax.

Example

  • Hello

  • World

Beispiel

  • Hallo

  • Welt

Markdown
Example [<]
  - Hello
  - World
Beispiel [v]
  - Hallo
  - Welt
Accordion

A collapsible can be opened as an accordion, using .

Example

  • Hello

  • World

Beispiel

  • Hallo

  • Welt

Markdown
Example [^]
  - Hello
  - World
Beispiel [v]
  - Hallo
  - Welt
Undecided

A collapsible can be controlled by Preferences, using .

Example

  • Hello

  • World

Markdown
Example [/]
  - Hello
  - World
Opted out

A collapsible can opt out of Preferences, using . Example

  • Hello

  • World

Markdown
Example [x]
  - Hello
  - World

Screen Images

Format: Webp
Size: 4096 x 4096 px
Quality: 90

Requires ImageMagick on your computer.

Install with brew
brew install imagemagick