AD Sliding FAQ vs SocraNext

AD Sliding FAQ creates a custom post type in order to create your FAQ. Once your FAQ posts are created you can add the FAQ in a page or a post with a shortcode, or in a template with a function. This plugin has been created with accessibility in mind. How-To To display your FAQ use the shortcode [sliding_faq] in a page or a post. By default, the questions are wrapped inside a H2 HTML tag. If you want to have H3 instead, just add the attribute heading to the shortcode, for example: [sliding_faq heading='h3']. You can create different topics for your FAQ using the custom taxonomy FAQ Topics, this way you can display multiple FAQ. To do so, add the topic attribute to the shortcode with the name of your topic(s), for example: [sliding_faq topic='Accessibility, SEO']. You can of course use both attributes: [sliding_faq heading='h3' topic='Accessibility']. Featured images are now supported and the default size is ‘thumbnail’. You can choose other dimensions size with the ‘size’ attribute: [sliding_faq size='large']. The attribute will support thumbnail, medium, large and full or any custom size. (Note that you’ll have to customize the CSS if you want to display a large image.) Translations You can translate AD Sliding FAQ on translate.wordpress.org. To-Do Turn the shortcode to a block Add Widget Support

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. – Knowledge Base page (WordPress page; default slug kennisbank-sn, configurable via the SocraNext platform). – Template-based rendering for single/archive and knowledge base 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. – 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. – POST /collection-slugs – sync configurable articles/knowledge-base URL slugs 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.