blog state

author

author is the only address allowed to write. Deliberately a constant rather than transferable ownership: this is one person's blog, and the same address is the only one the chain lets redeploy the realm anyway, so a second owner could publish posts it could never restore after a wipe.

realmPath

realmPath is this realm's own path, used to build the links Render emits.

maxSlugLen

maxSlugLen bounds a slug so a permalink stays typable and a key stays cheap.

excerptLen

excerptLen is how much of a post body the index shows.

introKey

introKey is the manifest key of the index header. It starts with '!', which validSlug rejects, so it can never collide with a post.

introSlug

introSlug is refused as a post slug. Not because this realm needs it: the intro lives in its own variable. It is refused so that the local half stays representable, where a post is \<slug>.md and the header is intro.md. A post published at this slug by a hand-written transaction would have no file it could live in, and tools/gnoblog would report it as an extra forever.

post

posts

// slug -> \*post

order

// "\<date>/\<slug>" -> \*post

intro

// markdown shown above the index

rev

// total writes accepted, bumped by every mutation

assertAuthor

validSlug

validSlug reports whether slug is a legal permalink: 1..maxSlugLen bytes of \[a-z0-9.\_-]. The character set excludes ':' and '/' so a slug can never break out of its own render path, and excludes uppercase so a post has exactly one URL.

validDate

validDate reports whether date is exactly YYYY-MM-DD. The format is not cosmetic: \`order\` relies on lexical order being chronological order, so a date of any other shape would silently sort into the wrong place.

orderKey

orderKey is the key a post takes in \`order\`. The slug is appended so two posts published on the same day do not collide.

splitTags

splitTags normalizes a comma-separated tag list: trimmed, lowercased, deduplicated, empties dropped. It returns the canonical string that gets stored, so the hash a client computes locally matches the one on chain.

joinTags

record

record is the canonical serialization a post hashes to. Both this realm and tools/gnoblog build it the same way, which is what lets one Manifest() read decide whether a local file needs a transaction at all.

hashOf

Set

Set creates or replaces the post at slug. This is the ordinary publish: one post, one transaction, idempotent. Changing the date moves the post in the index, so the old order entry is removed before the new one is written.

Append

Append adds to the end of a post's body. It exists for a body too large to fit in one transaction: Set the first chunk, Append the rest. An ordinary edit uses Set, which is idempotent and therefore safe to retry.

Delete

Delete removes a post and its index entry.

SetIntro

SetIntro replaces the markdown shown above the index. Passing "" restores the built-in header.

Get

Get returns a post's raw markdown body, or "" when there is no such post.

Count

Count returns the number of published posts.

Revision

Revision returns the total number of writes this realm has accepted. It changes on every mutation, so a client can cheaply tell "nothing moved".

Manifest

Manifest returns one tab-separated line per post, plus one for the intro: <slug>\t<rev>\t<date>\t<len of body>\t<sha256 of the canonical record> It is the diff surface tools/gnoblog reads with a single vm/qeval: the hash covers the title, date, tags and body together, so one read says exactly which local file needs a transaction without downloading a single body. The intro is reported under the key "!intro" with an empty date. '!' is not a legal slug character, so that row can never be confused with a post.

linkPrefix

linkPrefix is what a permalink starts with. gnoweb addresses a realm's render path with ':' after the package path, so this is realmPath with the leading "gno.land" dropped and the separator appended.

defaultIntro

defaultIntro is the header shown before SetIntro has ever been called, i.e. right after the first deploy or after a redeploy wiped the state.

Render

Render serves three views: "" the index, newest first "<slug>" one post "t/<tag>" every post carrying a tag

header

renderIndex

renderTag

renderPost

entry

entry is one row of a listing: linked title, byline, excerpt.

byline

byline is the date plus the post's tags as links, on one line.

hasTag

firstLine

firstLine returns the first non-empty, non-heading line of a body, which is what an excerpt should show: a post that opens with "## Something" would otherwise preview its own heading.