AI Chatbot for Pelican Sites

Technical Writing Ages Better Than It Is Found

A well-written post about a specific problem stays correct and useful for years. What decays is discoverability: search engines move on, the archive grows, and nobody browses.

Reading the archive and answering questions directly restores access without republishing anything. The writing was fine; the route to it was not.

Readers Have One More Question

An article explains an approach and the reader wants to know whether it applies to their version or their situation. There is usually nowhere to ask, so they leave.

Handling that question keeps them on the page and shows you exactly which paragraph to expand.

Python Environments Are Precious

Anyone maintaining a Pelican site has dealt with a build that broke because of an unrelated package upgrade. Adding another dependency is not attractive.

Nothing here touches Python. The generator, the plugins and the virtual environment stay exactly as they are.

Personal Sites Get Written in Bursts

Most personal technical sites are updated intensively and then left alone for months. Anything requiring routine attention will quietly break during a quiet period.

There is nothing to attend to here, which is what makes it appropriate for a site maintained in spare time.

Portability Matters Over a Decade

Generators come and go, and a site that lasts ten years usually gets migrated at least once. Integrations tied to a generator do not survive that.

Because this is one HTML line reading published output, it moves to whatever you use next with no work.