AI Chatbot for Pelican Sites
Pelican sites are usually written by the person who maintains them, in Python, deliberately. One line in the base template adds an assistant without adding a plugin to your pelicanconf.
Try it on your own site for free
Enter your Pelican site URL and see how an AI assistant would answer readers
See It In Action
For technical blogs and personal sites generated with Pelican
One Line in the Base Template
Pelican themes are Jinja templates you control. Add the tag to the base template and every article, page and index inherits it. No plugin entry, no pelicanconf change.
No Plugin, No Python Dependency
Pelican plugins are Python, which means version compatibility and another entry in your environment. This is HTML, so neither applies.
Answers From Years of Articles
Technical blogs accumulate solutions that are impossible to find later. The assistant reads the archive and answers directly, which makes old writing useful again.
Survives Theme and Generator Changes
Because it reads generated output, changing theme or even moving to another generator later costs one line re-added.
Thirty-Six Languages
Detected per reader, useful for technical writing that finds an international audience.
Have any questions? Try our AI chatbot right now
Ask it anything - it is live on this page
Built for Pelican Merchants
A Jinja edit and nothing else. pelicanconf stays closed.
One Jinja Edit
PLUGINS stays as it was and pelicanconf never opens.
Virtualenv Untouched
No wheel to resolve, so a working environment stays working.
Uses the Whole Archive
Old articles start answering questions again.
Portable
It reads output, so theme or generator changes barely matter.
36 Languages
Chosen from the reader’s message automatically.
No Invented Detail
It answers from your articles and admits gaps.
Simple Pelican Integration
One line in the base template covers the site. No plugin or config change.
-
1
Register and grab the line
Make an account, give it the address of the site so the crawler can work through your articles, and copy the line it hands you.
-
2
Open your theme base template
Add the tag before the closing body tag in the Jinja template your pages extend.
-
3
Rebuild as normal
Your usual invocation; the settings file is not involved at any point.
-
4
Everything else lives elsewhere
Register, standing instructions, extra reference files and colours are all set in the dashboard.
Sign up free and get your personalised snippet instantly - paste it once and the widget is live
Why Pelican Users Choose Asyntai
Start free with 100 messages, which covers most personal sites
Old Articles Earn Again
Solutions written years ago start reaching people who could not find them.
Nothing to Maintain
No plugin version, no dependency, no build change.
Ideas for What to Write
Reader questions show which gaps are worth an article.
Frequently Asked Questions
What Pelican users ask first
What an AI Assistant Adds to a Technical Blog
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.
Ready to Let Your Archive Answer Readers?
Start free with 100 messages and add one line to your theme.