Documentation hub for workflows, integrations, and implementation guidance
Use the docs area as the public-safe explanation layer for what the product can do, how the WordPress workflow works, and how teams should think about implementation.
WordPress workflow
Start with the WordPress workflow guide and then move to the plugin landing page.
API and webhooks
Use the API reference page and webhook guide for public-safe integration framing.
Features and blog
Use the features hub and the blog for workflow tutorials, strategic explainers, and product context.
Explain safe integration boundaries
Document approved workflows, authentication expectations, and machine-readable discovery without publishing sensitive internal surfaces.
Open API guidanceDesign completion callbacks that are reliable
Show how asynchronous workflow completion should be validated, retried, and connected to publishing or downstream automation.
Open webhook docsMap plugin operations to editorial review
Guide teams through setup, trigger, callback, and review steps so the WordPress publishing loop stays operationally safe.
Open workflow guideLLMs summary
Use llms.txt for a concise machine-readable summary of the public site.
LLMs full index
Use llms-full.txt for a larger Markdown index of public-facing pages, discovery assets, and recent WordPress blog summaries when the live feed is available.
AI crawler policy
Use ai.txt for crawler guidance, attribution policy, and training restrictions.
OpenAPI + plugin
Use OpenAPI and ai-plugin.json for AI-agent discovery.
Technical SEO
Read the technical SEO workflows guide.
Content planning
Read the search intent and content briefs guide.
AI discovery
Read the LLMs.txt and AI discovery guide.
Research planning
Read the research methodology planning guide.
Move between docs, workflow pages, and solution pages more deliberately
Workflow pages
Use the workflow hub to connect implementation docs to planning, governance, and publishing operations.
Open workflow pages →Solutions overview
Use the solutions hub when the main question is who the workflow is for and what operating model it supports.
Open solutions hub →Feature library
Use the feature hub when readers need concrete product capabilities tied to the docs and workflow layer.
Open feature hub →