From b171d00ceba32cd9372f2c748884474584e21f456445d12363c184deed81ded1 Mon Sep 17 00:00:00 2001 From: Nicholas Johnson <> Date: Fri, 18 Sep 2026 00:00:00 +0000 Subject: Add an example site The theme shipped no runnable site and documented no configuration, so every setting it reads had to be discovered by reading the templates, and there was nothing to build against when changing them. The build failure that unset RSS limits caused would have been caught immediately by an example site. The two configuration files are the separate website and capsule configurations the readme asks for, annotated with what each setting does and which are optional. The content demonstrates entries, tags, references, a standalone page and the front matter keys that control them. Also ignore build output, which no rule previously covered. Co-Authored-By: Claude Opus 5 --- exampleSite/content/about.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 exampleSite/content/about.md (limited to 'exampleSite/content/about.md') diff --git a/exampleSite/content/about.md b/exampleSite/content/about.md new file mode 100644 index 0000000..a75831d --- /dev/null +++ b/exampleSite/content/about.md @@ -0,0 +1,18 @@ +--- +title: "About" +draft: false +pageinfo: false +makerefs: false +build: + list: never +--- + +This is a standalone page rather than a journal entry. It sets +"pageinfo" to false, so no date or reading time is shown, and +"makerefs" to false, so its links are rendered in place. + +It also sets "build.list" to never, which keeps it out of the entry +list on the homepage and out of the feeds. + +Standalone pages are a good fit for a colophon, a contact page or a +now page. Link to them from the menu in your configuration file. -- cgit v1.2.3