SocraNext

What the plugin provides
– Custom Post Type socranext_post (slug: artikelen-sn) for AI-optimized articles.
– Custom Taxonomy socranext (hierarchical) for categorizing those articles.
– Knowledge Base page (WordPress page, slug kennisbank-sn).
– Template-based rendering for single/archive and knowledge base views (plugin templates via template_include).
– Admin screens under SocraNext (Overview, Articles, Knowledge Base, Pages) including per-page FAQ toggles.
– Cache flush on (de)activation to correctly register permalinks.

Display
The plugin renders views via bundled templates for:
– Single SocraNext articles and archive list
– Knowledge base page with categories and Q&As

Structured Data
– The FAQ display includes FAQPage JSON-LD to help search engines and AI systems better understand the Q&As.

REST API (for platform integration)
Under the namespace socranext/v1, routes include:
– GET /pages and GET /pages/{id} – list site pages (for adding/showing FAQ widgets).
– POST /toggle – enable/disable the FAQ widget per page.
– POST /store-aio-information and GET /aio-information/{page_id} – store/retrieve per-page FAQ data.
– POST /kennisbank and POST /kennisbank-custom – store knowledge base categories and custom markup/styles.
– POST /blog and POST /store-blog-custom – create articles and store global custom HTML/CSS/JS for article display.
– GET /articles-list-custom – retrieve configuration for list views.

Note: without an account/connection to app.socranext.ai, the auto-generation routes are typically not used, but the created post types, taxonomy, and pages remain available for display.

Privacy & external services
– The plugin does not call external APIs on its own; the integration is typically initiated by the SocraNext platform to your website.
– Websites: product site https://socranext.ai and platform https://app.socranext.ai.

Prefix & naming policy

• All plugin identifiers use the unique prefix family “SocraNext”:
  • Functions, hooks, options, AJAX actions, REST namespace, script/style handles: socranext_* (lowercase)
  • Constants: SOCRANEXT_* (uppercase)
  • Human-facing labels and PHP namespaces (if used): SocraNext (PascalCase)
• We avoid reserved prefixes like wp_, _, and __ for custom identifiers.
• Existing options and routes already comply; no migrations are required.