Every WPsigner docs page has a matching Markdown twin built for AI assistants. Use it when Ask AI is unavailable, when you work in Cursor/ChatGPT/Claude, or when you want a portable offline reference.
Fastest path
Section titled “Fastest path”- Open any documentation page.
- Click Copy for AI under the title.
- Paste into your assistant with a prompt like:
You are helping me configure and use WPsigner, a self-hosted electronic-signature plugin for WordPress.Use ONLY the documentation I paste as your source of truth.If something is not covered, say so clearly.Prefer exact admin menu paths, shortcodes, endpoints, and settings names from the docs.You can also click View Markdown to open the .md file in the browser and copy it manually.
What we publish for AI
Section titled “What we publish for AI”| Resource | URL | Best for |
|---|---|---|
| Per-page Markdown | /md/{slug}.md | One feature or integration |
| Lite pack | /md/packs/lite.md | Lite-safe pages only (edition: both + Lite hubs) |
| Topic packs | /md/README.md (packs listed there) | Setup, security, API, integrations, addons |
| Complete pack | /md/packs/complete.md | Full docs in one file |
| Markdown index | /md/README.md | Catalog of every page + pack |
| LLM sitemap | /llms.txt | Crawlers and agent discovery |
| Full corpus text | /llms-full.txt | Large-context models |
HTML and Markdown are generated from the same source files. If a page exists in the docs, it has a Markdown twin. Every /md/{slug}.md file starts with edition: lite, edition: pro, or edition: both so assistants do not invent Pro features for Lite users.
Recommended packs
Section titled “Recommended packs”| Pack | Use when |
|---|---|
| Lite | WordPress.org / Lite questions — excludes Pro-only pages |
| Setup | Installing, hosting, first document, system status |
| Security | Roles, OTP/KYC, Digital ID, TSA, audit, storage |
| Core features | Documents, campaigns, portal, workflows, fields |
| API | REST endpoints, auth, webhooks, examples |
| Integrations | Forms, Fluent Community, CRM, storage, automation |
| Addons | Document Builder, Smart Forms, MainWP, Uncanny Automator, importers |
| Customization | Branding, emails, languages |
| Support | Troubleshooting, FAQ, security disclosure |
| Complete | Everything (large — use only if the model allows) |
Example URLs
Section titled “Example URLs”Machine-readable map: /md/manifest.json
Prompt recipes
Section titled “Prompt recipes”Configure a feature
Section titled “Configure a feature”I am setting up WPsigner on my WordPress site.Using only the Markdown below, give me a numbered checklist with exact admin paths and settings.Ask me for any missing site-specific details (domain, SMTP, plugins already installed).
<PASTE MARKDOWN OR PACK>Debug an error
Section titled “Debug an error”WPsigner shows this error: <PASTE ERROR>Using only the documentation below, list the most likely causes and the exact checks to run.Do not invent menu names or endpoints that are not in the docs.
<PASTE MARKDOWN OR PACK>Build an integration
Section titled “Build an integration”I need to connect WPsigner to <SERVICE>.Using only the documentation below, outline prerequisites, configuration steps, webhooks/events, and test plan.
<PASTE INTEGRATIONS OR API PACK>Completeness guarantees
Section titled “Completeness guarantees”On every production build we verify:
- Every docs source file is exported to
/md/and the Ask AI corpus. - The complete pack includes every page (no omissions).
- Named packs only reference slugs that exist.
llms.txtandllms-full.txtare regenerated from the same source set.
If a Markdown twin is missing for a page, treat it as a docs build bug and report it.
Related resources
Section titled “Related resources”- Troubleshooting
- FAQ
- Glossary
- Lite vs Pro
- REST API Overview
- Docs LLM index: docs.wpsigner.com/llms.txt
- Product LLM summary + pricing: wpsigner.com/llms.txt · Pricing