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 <noreply@anthropic.com>

1 files changed, 20 insertions, 0 deletions

diff --git a/exampleSite/content/entry/tagging.md b/exampleSite/content/entry/tagging.md
new file mode 100644
index 0000000..caef813
--- /dev/null
+++ b/exampleSite/content/entry/tagging.md
@@ -0,0 +1,20 @@
+---
+title: "Tagging"
+date: 2026-03-08T11:00:00+0000
+draft: false
+tags: ["journal", "gemini"]
+makerefs: false
+---
+
+Tags are listed alongside the date and reading time of an entry, and
+each one gets a page and a feed of its own.
+
+This entry sets "makerefs" to false, so its links are rendered where
+they appear rather than being collected at the foot of the page. In
+gemtext a link must occupy a whole line, so only links written on their
+own line become link lines:
+
+[The tag list for this site](/tags/)
+
+Set "showlinkemoji" to false in the front matter to drop the link emoji
+from those lines.