PubPla AI Help Center vs SocraNext

This plugin add new custom post type ‘FAQ’. With some functionality, you can build help center for your user. What is help center? We collect examples at our github wiki. Live demo: https://demo.kunoichiwp.com/pubplafaq/ — Try the AI Overview on the front page. The demo is in Japanese, built around a fictional anti-aging subscription “Jovian”, but you can still get a feel for how the AI answers real questions from your FAQ content (and admits when something isn’t covered). Creating Portal This plugin will provide… Custom post type with single page and archive page. Custom taxonomy associated to CPT. Incremental search box. AI Overview(Since 2.0.0) AI Overview AI Overview answers user questions based on your FAQ content using a large language model. It uses the wp-ai-client bundled with WordPress core since WordPress 7.0, which requires an AI service to be configured in WordPress. Requirements: AI Overview requires WordPress 7.0 or later. On older WordPress versions, the AI Overview block and template function will still appear in the editor and on the front-end, but the search form will not work (the REST endpoint that powers it is disabled). Other features of this plugin (FAQ custom post type, incremental search, shortcode) continue to work on WordPress 6.6+. Upgrade WordPress to 7.0 to enable AI Overview. You can configure AI behavior and rate limiting from Settings > Help Center in the admin panel. The settings page also includes a Rebuild Catalog Now button to manually refresh the FAQ catalog used as LLM context. The Catalog The catalog is the set of posts handed to the LLM as context. It is the union of several queries, merged and deduplicated by post ID: Every published post of a supported post type. These can be cited, so they appear under Sources in an answer. Every private post assigned to the default term of the AI Catalog taxonomy. These are background material: their text is used to answer everyone, but they are never cited and never linked. Use this for internal knowledge you do not want as a standalone public page. To add sources of your own — other post types, a taxonomy filter, a meta condition — use the hamelp_catalog_sources filter. Each source is a get_posts() argument array plus a citable flag; earlier sources win on duplicates. add_filter( 'hamelp_catalog_sources', function ( $sources ) { $sources['pages'] = [ 'args' => [ 'post_type' => [ 'page' ], 'post_status' => [ 'publish' ], ], 'citable' => true, ]; return $sources; } ); Using the Block Add the AI FAQ Overview block in the block editor. The block has the following options: Placeholder — Input placeholder text. Button Text — Submit button label. Show Sources — Display related FAQ links below the answer. Using the Template Function You can also use hamelp_render_ai_overview() in your theme templates: The function accepts an optional array of arguments: 'Ask a question...', 'button_text' => 'Ask AI', 'show_sources' => true, ] ); ?> The function automatically enqueues the required JavaScript and CSS assets. Search Box The incremental FAQ search box is available in three forms. Using the Block Add the FAQ Search Box block in the block editor. The block has the following options: Label — Input placeholder text. Button Text — Submit button label. Using the Shortcode You can use shortcode hamelp-search in page content. [hamelp-search label='Enter your question here.'][/hamelp-search] Using the Template Function You can also call hamelp_render_search_box() directly from your theme templates: 'Enter your question here.', 'btn' => 'Search', ] ); ?>

What the plugin provides – Custom Post Type socranext_post for AI-optimized articles (default URL slug artikelen-sn, configurable via the SocraNext platform). – Custom Taxonomy socranext (hierarchical) for categorizing those articles. – Template-based rendering for single/archive article views (plugin templates via template_include). – Admin screens under SocraNext (Overview, Articles, Categories). FAQ management is handled via the SocraNext platform. – Cache flush on (de)activation to correctly register permalinks. Display The plugin renders views via bundled templates for: – Single SocraNext articles and archive list. Structured Data – The FAQ display includes FAQPage JSON-LD to help search engines and AI systems better understand the Q&As. – SocraNext articles output their own SEO title, meta description, Open Graph tags and Article JSON-LD (independent of third-party SEO plugins; mirrored into Yoast / AIOSEO / Rank Math when present). 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 /blog and POST /store-blog-custom – create articles and store global custom HTML/CSS/JS for article display. – POST /collection-slugs – sync the configurable articles URL slug from the SocraNext platform (rewrite flush + cache purge). – GET /articles-list-custom – retrieve configuration for list views. – POST /llmstxt and GET /llmstxt – publish and read llms.txt / llms-full.txt content from the SocraNext platform; served at /llms.txt and /llms-full.txt on the site. 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.