lektor-ai-chatbot
Add the Asyntai AI chat assistant to your Lektor site. It answers visitor questions from your own content, day and night.
Install
lektor plugins add lektor-ai-chatbot
Then create the file configs/ai-chatbot.ini in your project:
widget_id = asyntai_1a2b3c4d5e6f
Build the site. The chat bubble is on every page.
Where the widget ID comes from
Open the Install page in your Asyntai dashboard.
The widget ID is the value of data-asyntai-id in the snippet shown there. It
starts with asyntai_.
Creating an account is free, and the Free plan is enough to try the widget.
Options
All options go in configs/ai-chatbot.ini.
| Option | Default | What it does |
|---|---|---|
widget_id |
required | Your Asyntai widget ID |
enable_on_server |
true |
Set to false to keep the widget off the site during lektor server |
script_url |
the Asyntai CDN | Advanced. Load the widget from another URL |
A missing or malformed widget_id stops the build with a message that says how
to fix it.
What the plugin does
- It adds one
<script>tag in front of the closing body tag of every HTML page that Lektor builds, including paginated pages and the 404 page. - It marks the tag
async, so your pages render first. - It changes nothing else. No templates are overridden and no CSS is added.
- Feeds, sitemaps, CSS and images stay as they are. An HTML file in
assets/gets the widget only when it is a full page. - If a page already has the Asyntai snippet, for example in a template, the plugin leaves that page alone.
Answering from your content
Asyntai reads your published pages. Add your site URL in the dashboard, and the assistant answers from the same pages the widget sits on. You can also add documents, and question and answer pairs.
Removing it
Run lektor plugins remove lektor-ai-chatbot and build again. The widget is
gone.
Support
Email hello@asyntai.com, or read the Lektor guide.
Licence
MIT. See LICENSE.
1 maintainer
Metadata
1 maintainer
Release files for lektor-ai-chatbot 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| lektor_ai_chatbot-1.0.1.tar.gz | 9.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| lektor_ai_chatbot-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.3 kB
Release files / lektor_ai_chatbot-1.0.1.tar.gz
| Download URL | lektor_ai_chatbot-1.0.1.tar.gz |
|---|---|
| Size | 9.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
19462d9196539435bc5de75b3956c2611f34518b2980b93dcc41e728a49d37ef
|
|
BLAKE2b-256 checksum How to use checksums |
d66b08bf6554c6c4dde9b3dad7fef0ecaaf2989eae4e6e23c453e32426c89275
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.10
|
Release files / lektor_ai_chatbot-1.0.1-py3-none-any.whl
| Download URL | lektor_ai_chatbot-1.0.1-py3-none-any.whl |
|---|---|
| Size | 5.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e64da8334e9275c3770c2f0dd1627745703f947c77dd8983006235a7affcc767
|
|
BLAKE2b-256 checksum How to use checksums |
d968644cc80b0253be72c498bd1ca9ad6d86f34eb1aae66113ad33abcfbd08a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.10
|
Security for lektor-ai-chatbot 1.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
