This can be avoided easily (while still leaving it rendered for an actual 400 Not Found situation) by adding:

_build:
  list: never

to the frontmatter of the 400/index.md file.

It probably should also be excluded from search, but I'm not sure how to do that yet.

Explain the content generation for:

• Short breadcrumbs
• Page title
• Subtitle
• Date of first publication, which should also link to the GitHub source

Where is the best place to document the highlighting shortcode?

• Besides the syntax of fenced code blocks (basic -> code)
• In shortcode -> built-in -> internal

Hi Georg,

that's no big deal but in the footer of the demo site a link points to "Impressum". This page is 404

All the best

I noticed that the social and follow icons only allow one to use branded targets. It would be great to be able to use custom (non-Simple) icons for follow and contact where they don't fit into a 'brand'. (@danielfdickinson)

Describe different types of archetypes for single content files and page bundles.

The content should be part of the example site as well as the full site

The navigation is generated from front-matter parameters. There purpose and function needs to be documented.

• title
• description
• menu (different kinds of)
• weights (page weight or menu weight)
• taxonomies

• change new command for leaf bundle. archetype for folder!

• List the current features of Perplex

• Get the standard Markdown page for Hugo themes

• Add notes leading to alternatives provided by Perplex