Different ways to publish an idea
Blog, Logs, Labs, Docs, and Book are optional conventions, with different reading patterns rather than a required taxonomy.
A long article, a quick observation, and an interactive experiment ask different things of a reader. Giving them different homes can make a site easier to use without turning every entry into a categorization exercise.
Alkemist now demonstrates five optional sections. Blog holds developed writing. Logs makes short notes easy to scan. Labs contains interactive apps and experiments. Docs is reference for the project. Book offers a deliberately ordered starting point. Info stays the home for project background.
Reference and a reading path
Docs is useful when you already know the question: which property selects a chart axis, where a configuration value lives, or how a deployment works. A book is useful when you want a sequence: choose a scope, make one page, try an interaction, and publish it.
The book links to reference pages when they become relevant. It does not need to repeat them. Its chapters have a deliberate order and previous/next links; changing a chapter’s order does not change its address.
A smaller place for small observations
A log is an entry that benefits from being published before it becomes a full article. The feed shows its content, date, and permanent link so a reader can scan recent observations without opening every item. Drafts stay out of the public feed and routes.
A log can inspire an article later. Keep the original address and link the two. Existing blog entries are not being moved merely because their subject resembles a devlog or note.
Choose a shape for your own project
These are conventions, not required sections. A small experiment might use only Labs and Info. A tutorial project might center its Book. A research notebook might use Blog and Logs without a documentation section.
The source starter owns section configuration, navigation, sample content, and routes in the generated application. Disabled starter sections do not generate pages, while their source content remains available. Labels can change independently of route names. The shared component packages do not impose a content taxonomy.
The updated scaffold is available through the source generator. The published create-alkemist@1.0.0-beta.1 is unchanged; these additions will enter a later deliberate package release. Existing generated sites remain theirs to edit and migrate.