AI Chatbot for Nikola Sites

Translation Is Finite, Support Is Not

Translating a post is a task with an end. Answering questions about it in three languages is open-ended, and depends entirely on whether the author is around.

That asymmetry is why multilingual sites usually have one well-supported language. An assistant removes it, because answering costs the same in every language.

Partial Translations Are Normal

Almost every multilingual site has gaps: newer posts translated, older ones not, or vice versa. Readers arriving in the incomplete language see less than they hoped.

Answering from whatever content exists, in their language, closes part of that gap without any additional translation work.

Source Formats Change More Than Output

Nikola users switch between reStructuredText, Markdown and notebooks depending on the post. Anything reading source has to handle all of them.

Reading the generated HTML avoids that entirely: however you wrote it, the published page is the same kind of artefact.

Reproducible Builds Are the Point

People who choose Python static generators tend to care about builds that behave identically next year. Every dependency is a threat to that.

Nothing enters the environment here, so reproducibility is unaffected and the site can still be rebuilt years later.

One Line Is Portable

Sites outlive their generators. A decade-old site has usually been migrated at least once, and integrations rarely survive.

A single HTML tag reading published output moves to whatever comes next with no work at all.