content models

Putting your content in a repository looks like a tooling preference. It is actually a choice about consistency, history and who is allowed to write — and it has a specific expiry date you should decide in advance.

A feed costs a few dozen lines, requires no keys, no versioning and no support, and gives every consumer — reader, aggregator, script or agent — the same view of your archive. Almost nobody ships one properly.

Categories, subcategories and tags look like three flavours of the same idea. They are three different promises about permanence, and confusing them is how a site ends up with two answers to what a page is about.

A calendar day and an instant in time are different types, and most date bugs are the moment one is silently converted into the other. The fix is not better formatting — it is refusing the conversion.