FULSTK

Most canonical bugs are not tagging mistakes. They are a site accidentally telling search engines that all of its pages are the same page — and the defaults in every framework make that the easy thing to do.

Schema.org markup is usually treated as an SEO garnish you add at the end. It is better understood as a set of machine-readable promises about a page — which means the interesting question is what happens when the page stops keeping them.

Optimising for language models is mostly framed as writing for a new kind of reader. The more useful frame is that you are now writing for a reader that has to decide whether to stake its answer on you.

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.

Your direct dependencies are a decision. Everything underneath them is a consequence — and on a typical install, the consequences outnumber the decisions by two orders of magnitude.

The value of a component library is not the components. It is the set of decisions it takes off the table — and a system that keeps saying yes to variants has given that value away.