Mos FAQs
A simple FAQ plugin that lets you create FAQs, order FAQs, publicize FAQs, etc. It uses custom post types and taxonomies to manage an FAQ section for your site. You can display your every FAQ section in 3 different ways accordion, collapsible, and block view. Includes shortcode options for different display configurations. FAQ KEY FEATURES Mos FAQs, with unlimited tag and category support Create FAQ categories and tags Create FAQ posts and assign categories and tags to them Easy design layout to style your FAQ posts Responsive FAQ design that looks great on all screen sizes For advanced user additional CSS and JS input panel for adding custom scripts And the most important thing it will not add any additional time on your page load time [mos_faq] Simply insert the above short-code into any page to display your FAQs. Mos FAQs can do more than just FAQs. If you have a help desk or knowledge base and need to pass on information to your visitors and/or users, the question/answer formatting is perfect. With the various options related to toggling, as well as the custom fields functionality, you can easily create an in-depth knowledge base and help desk. Mos FAQs has a responsive design that makes your FAQs look good on all screen sizes and all devices. No more worrying about what your mobile FAQs might look like. All options and styling will be applied across all devices, so you can focus on your content. A few extra seconds could have a huge impact on your ability to engage visitors and make sales. This means that having a fast site is essential — not just for ranking well with Google, but for keeping your bottom-line profits high. So losing page speed for a plugin is a very pain full experience, by default Mos FAQs plugin fully optimized and it will not add any additional load into your website. SHORTCODE [mos_faq] This short-code accepts a lot attributes, the attributes controls what to display and how to display your FAQs. Description of attributes in short is given below limit: (int) – number of post to show. Use ‘limit’=>-1 to show all FAQs (the ‘offset’ parameter is ignored with a -1 value). offset: (int) – number of post to displace or pass over. The ‘offset’ parameter is ignored when ‘limit’=>-1 (show all FAQs) is used. category (string) – category ids separate by , tag (string) – tag ids separate by , order (string) – Designates the ascending or descending order of the ‘orderby’ parameter. Defaults to ‘DESC’. An array can be used for multiple order/orderby sets. ‘ASC’ – ascending order from lowest to highest values (1, 2, 3; a, b, c). ‘DESC’ – descending order from highest to lowest values (3, 2, 1; c, b, a). orderby (string) – Sort retrieved posts by parameter. Defaults to ‘date (post_date)’. One of ID, author, title, name, type, date, modified, parent, rand, comment_count these options can be passed. author (int | string) – use author id or comma-separated list of IDs. container (string) – Whether to wrap the FAQs section, and what to wrap it with. Default ‘div’. container_class (string) – Class that is applied to the container. class (string) – CSS class to use for the container of FAQs. view (string) – One of accordion, collapsible, and block these options can be passed. grid (int) – One of 1, 2, 3, 4, and 5 these options can be passed. pagination (int) – If necessary then use 1 if not then leave this attribute or use 0. singular (int) – If necessary then use 1 if not then leave this attribute or use 0.
Top keywords
- faqs16×2.68%
- faq10×1.68%
- string9×1.51%
- int6×1.01%
- mos6×1.01%
- options6×1.01%
- order6×1.01%
- display5×0.84%
- class4×0.67%
- container4×0.67%
- mos faqs4×0.67%
- parameter4×0.67%
SocraNext
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.
Top keywords