LemonX Knowledge custom post type
This capability maps to the /kb, /kb/retrieve surface and gives WordPress operators a concrete action rather than an abstract feature.
Knowledge RAG
Knowledge Base & RAG for WordPress.
Build a WordPress-native knowledge base that AI workflows can retrieve from before generating pages, articles, media prompts or brand-specific copy. Registers a LemonX Knowledge post type and exposes entries, library, retrieval, embeddings and site-profile endpoints.
Rendered for real WordPress use
A B2B site imports product pages, brand guidelines and service FAQs into the KB, so the AI Copilot and Writer can gene
Version OKA B2B site imports product pages, brand guidelines and service FAQs into the KB, so the AI Copilot and Writer can gene
Product role
What this page should communicate.
Knowledge Base & RAG is part of LemonX Code, the React-based WordPress page and code editor. The feature should be presented as a practical workflow, not a loose AI promise. It helps teams handle RAG work while staying close to WordPress permissions, saved content, template behavior and front-end rendering. For website owners, that means less hand-copying between tools. For agencies, it means a repeatable production process that can be explained, reviewed and handed off.
This product page is written for WordPress users who need to understand both the value and the operational workflow. It connects the marketing promise to the actual plugin surface: admin pages, REST endpoints, permissions, WordPress records and front-end rendering behavior.
- Keep product facts and brand rules in separate entries.
- Disable outdated entries instead of deleting useful history.
- Test retrieval before relying on AI drafts.
Scenario: A B2B site imports product pages, brand guidelines and service FAQs into the KB, so the AI Copilot and Writer can generate on-brand, context-aware pages.
Key capabilities
/kb, /kb/retrieveFeature details grounded in the LemonX Code plugin.
These are not generic builder claims. They reflect how LemonX Code exposes real WordPress admin screens, REST endpoints, services, records and rendering workflows.
Entry create, delete and toggle endpoints
This capability maps to the /kb, /kb/retrieve surface and gives WordPress operators a concrete action rather than an abstract feature.
Library ingestion and export
This capability maps to the /kb, /kb/retrieve surface and gives WordPress operators a concrete action rather than an abstract feature.
RAG retrieval endpoint
This capability maps to the /kb, /kb/retrieve surface and gives WordPress operators a concrete action rather than an abstract feature.
Embeddings test and site profile endpoints
This capability maps to the /kb, /kb/retrieve surface and gives WordPress operators a concrete action rather than an abstract feature.
Workflow
How a WordPress operator uses it.
Each workflow is designed around an actual WordPress task: creating, editing, importing, publishing, testing, securing or reporting work inside the site environment.
| Step | Action | Operational detail |
|---|---|---|
| 1 | Add knowledge entries | Add knowledge entries is handled as part of the Knowledge Base & RAG workflow so the operator can move from intention to reviewed WordPress output without switching tools. |
| 2 | Ingest URLs or files | Ingest URLs or files is handled as part of the Knowledge Base & RAG workflow so the operator can move from intention to reviewed WordPress output without switching tools. |
| 3 | Sync site content | Sync site content is handled as part of the Knowledge Base & RAG workflow so the operator can move from intention to reviewed WordPress output without switching tools. |
| 4 | Generate embeddings | Generate embeddings is handled as part of the Knowledge Base & RAG workflow so the operator can move from intention to reviewed WordPress output without switching tools. |
| 5 | Retrieve context during AI work | Retrieve context during AI work is handled as part of the Knowledge Base & RAG workflow so the operator can move from intention to reviewed WordPress output without switching tools. |
Implementation surface
LemonX CodeRoutes, records and WordPress context.
This section helps users understand where the feature lives inside the plugin and what type of data or behavior it controls.
| Surface | What it does | Why it matters |
|---|---|---|
| Primary route or service | /kb, /kb/retrieve | Shows the real plugin surface behind this product page. |
| WordPress context | Registers a LemonX Knowledge post type and exposes entries, library, retrieval, embeddings and site-profile endpoints. | Explains how users encounter the feature in the admin, editor, front end or records layer. |
| Best fit | Knowledge | Helps visitors understand where the feature belongs in the LemonX Code suite. |
| Version alignment | LemonX Code v1.1.50 | Keeps the page consistent with the current plugin package and download expectation. |
Use cases
Where this feature creates value.
The same LemonX Code module can serve creators, agencies, business websites, ecommerce teams and developers depending on the workflow.
01
Brand-grounded AI
Give Copilot and Writer access to product facts and brand guidelines.
02
Site understanding
Sync existing pages so AI references correct URLs and terminology.
03
Document intake
Turn briefs, PDFs and client files into reusable context.
04
RAG workflows
Retrieve the right context before generating pages or posts.
Best practices
Use it safely in production WordPress sites.
Knowledge Base & RAG should be treated as a production workflow. The goal is not to generate something once, but to create an output that can be reviewed, maintained, reused and handed off inside WordPress. The safest approach is to keep source data clear, confirm the result visually, and avoid applying broad changes without a preview.
- Keep product facts and brand rules in separate entries.
- Disable outdated entries instead of deleting useful history.
- Test retrieval before relying on AI drafts.
FAQ
Common questions about Knowledge Base & RAG.
Does KB store content inside WordPress?
Yes. Knowledge Base & RAG is designed around WordPress admin screens, permissions, records or REST endpoints rather than a detached external interface.
Can it ingest URLs?
Knowledge Base & RAG should be used as a structured WordPress workflow: configure the source, run the action, review the output, then apply it safely to the site.
What is RAG used for?
Knowledge Base & RAG should be used as a structured WordPress workflow: configure the source, run the action, review the output, then apply it safely to the site.
Build faster with Knowledge Base & RAG.
Use LemonX Code v1.1.50 to turn knowledge base & rag into a repeatable WordPress workflow with real admin screens, REST-backed actions, review states, reusable outputs and clean front-end rendering.