A template override and a button on your Zensical site. Users ask questions in plain language and get source-linked answers from the content you’ve already written.
Used by documentation and developer-experience teams
What it does
Add the widget through Zensical’s custom_dir template override. the same mechanism Material for MkDocs uses. One overrides/main.html, no plugin, no build changes to the rest of your site.
Biel retrieves from indexed documentation and links to the sources behind an answer. Readers can open those pages to check details or continue reading.
If your docs don't cover a question, the bot can say so and show a support email, contact form, or another next step you configure.
Code blocks, config snippets, error messages, and API references are parsed as structured content. Readers can ask about those examples and follow the answer back to the documentation. Check generated code before using it.
Reads English docs, answers in Spanish, French, Japanese, Portuguese, German, and 30+ more. Readers can ask in their preferred language and follow the supporting source links.
Refresh sources manually or use the schedule included in your plan. You can also trigger indexing through the API when your site is published; API access requires Business or Enterprise.
Sign up, connect your documentation, test answers, and add the widget through a Zensical template override.
Built for Zensical and Material for MkDocs. see the full Zensical install guide.
{# overrides/main.html. Zensical template override #}
{% extends "base.html" %}
{% block extrahead %}
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/
biel-search/dist/biel-search/biel-search.css">
<script type="module" src="https://cdn.jsdelivr.net/npm/
biel-search/dist/biel-search/biel-search.esm.js"></script>
{% endblock %}
{% block content %}
{{ super() }}
<biel-button project="YOUR_PROJECT_ID" button-style="dark">Ask AI</biel-button>
{% endblock %}Use cases
Zensical reads your existing mkdocs.yml and template overrides, so the Biel widget you ran on Material for MkDocs keeps working. Point custom_dir at your overrides and rebuild. Keep your existing project and source configuration.
Help developers find the setup instructions, API reference, or configuration guide they need while using your product. Biel answers from the documentation you connect.
Let users ask in plain language and receive a source-linked answer. When the docs do not cover the question, show a support path you configure.
Connect the supported chat apps on a plan that includes them. Team members can ask about the same indexed documentation in channels where the bot is available.
“Easy to set up, yet the positive effects are felt immediately.”
zensical.toml or mkdocs.yml. Your docs stay on Zensical.