SpicaSEO 內容引擎路線圖：打造引擎，而非逐篇撰寫文章

Update (Oct 2026): CryptoCardCompass now lists 54 cards.

Around twenty of our own sites, one person deciding what they say. You can keep writing every page by hand and drown politely, or you can build the thing that writes, checks and ships them, and then spend your evenings arguing with it instead. The next months go into the second option: one typed content pipeline, one design language across the sites, and a fact-check gate that is allowed to say no. This is a roadmap, not a victory lap. The design work is out in the world. The engine and the gate are still being built and tested.

Why stop writing posts one by one

Every site started as its own small kingdom. Its own CMS habits, its own idea of what a guide looks like, its own way of being slightly wrong. Fixing one meant fixing it nineteen more times, usually by memory, usually at night.

The interesting work is not the next article. It is the machinery that knows what an article on this site is allowed to contain, where it gets its facts, and who has to look at it before it goes out.

• Content gets a type and a schema, not a blank text box.
• Every generated field should carry where it came from.
• Publishing becomes a separate step with its own rules.
• Live content gets refreshed instead of quietly rotting.

Writing the twentieth guide by hand is not craft. It is a cry for help with good grammar.

The roadmap, in order (in progress)

1. Typed content storage so a review is a review and a glossary term is a glossary term.
2. Generation directed by that schema and every field keeps its provenance.
3. A publication step that talks to our own CMS and to WordPress or custom sites through adapters.
4. Autopilot per content type, only where the type has earned it.
5. Refresh of live pages and follow-ups only after publication is verified.
6. One design language rolled across the sites so the engine is not dressing each one by hand.

Before and the plan for after

The test case: artist bios that refuse to guess

DROP THE BASS is where the gate is being tested first. The artist bio pipeline we are building writes only bio fields and drops claims it cannot support. No invented residencies, no imaginary label history, no "legendary" unless something actually says so. It is not running in production yet. It is the place where we find out whether the gate is strict enough.

Spotify and YouTube matching by ID instead of by name is part of the same work. Plenty of artists share a name with someone who makes very different music, and matching by name is how a jungle producer ends up linked to a wedding band. An ID ends that argument.

The gate can say no

A fact-check that always passes is decoration. The bio gate we are testing drops unsupported lines and leaves the field shorter. A short true bio beats a long beautiful lie every single time.

One design language and many accents

This part is already out. VPNScoreLab, Brokeli, CoinFaro and ProxyLister got new design systems in the last weeks, and SpicaSEO got its own refresh. They should not look identical. They should feel like they come from the same workshop.

Brokeli now speaks eight languages, with calculators, lessons and a glossary. CoinFaro grew a real glossary and guides. That volume only makes sense if the engine underneath stays honest, which is exactly why the engine comes next.

Quality gates before anything goes live

• Every factual field has a source the engine can point to.
• Unsupported claims are dropped and not softened.
• External profiles are matched by ID and not by name.
• The page fits the site's design language.
• Publication is verified before any follow-up runs.
• A person can see what changed and roll it back.

What is honestly still in progress

The content engine in SpicaSEO and the new connector for our own CMS are in progress. Nothing here is shipped as a finished machine. Adapters come for our own CMS first, then WordPress and custom sites. Autopilot will be per content type and no type has earned it yet. The bio gate on DROP THE BASS is in testing, not in production.

A couple of new sites will grow up on this engine from day one. SpicaVPN is prelaunch with a waitlist. CryptoCardCompass is an early catalog with nothing published yet.

Every new site still gets a real review before it opens. The engine prepares. A person decides.

Why roadmap and not launch

We would rather publish where the engine is going and get corrected than announce a finished machine that still needs a babysitter. When pieces ship they go to the Friday Dev Log.

The bet

Fewer hand-made posts. More time on the engine and the gates. If it works, twenty sites stay honest with the same effort as two. If it does not, at least it fails loudly and in one place.

Originally published on the Spicanet blog: https://spicanet.dev/blog/build-the-engine-not-the-posts