4WP FAQ

Source: github.com/4wpdev/4wp-faq · More plugins: 4wp.dev/plugins

How to work with it (short path)

1. 01In the editor, add a core Accordion (or select an existing one).
2. 02Click Convert to FAQ in the block toolbar (or insert the 4WP FAQ block). You can also select existing Details , Accordion , or heading + paragraph blocks and use Transform to → 4WP FAQ .
3. 03Put the question in the Accordion Item heading and the answer in the panel.
4. 04Open FAQ → Settings and enable FAQPage JSON-LD if you want structured data on the front end.
5. 05Optional: complete registry setup → Rescan (Dashboard or Settings) → place 4WP FAQ List and 4WP FAQ Categories on a hub page or template.
6. 06Optional: FAQ → Add FAQ — question, answer, FAQ categories (every matching FAQ block) and/or one page. No place chosen: the row is registry-only until a scan drops it.
7. 07Optional: edit a registry FAQ and Update — the plugin writes that item onto every Used In page (question match uses the previous title if you renamed it).
8. 08Optional: configure Settings → Connectors , then FAQ → Settings → AI to allow field markup. On FAQ → Categories , edit a term and Generate with AI . Apply writes into the form; Update still saves.

The registry is a helper. Accordion items on pages are the source of truth. A scan rebuilds the CPT from the site. New answers reuse the markup wrapper of a sibling accordion item on that page.

Blocks

• 4WP FAQ ( forwp/faq ) — wrap Accordion / Accordion Item for JSON-LD and registry scan
• 4WP FAQ List ( forwp/faq-list ) — registry glossary: grouped or flat, include/exclude categories
• 4WP FAQ Categories ( forwp/faq-categories ) — category nav that filters the List; nested terms collapse by default
• 4WP FAQ Count ( forwp/faq-count ) — live count for All / category / search ( [forwp_faq_count] )
• 4WP FAQ Card ( forwp/faq-card ) — inner card for the List (not in the inserter)

Key features

• Wrap Accordion / Accordion Item (legacy Details still supported)
• FAQPage JSON-LD in the document head — site-wide toggle plus per-block override
• Optional FAQ registry — scan, Used In , edit-to-push, Add FAQ onto category pages or one page
• FAQ categories — manage in admin, assign per block, or create on scan from the page
• Admin Dashboard — status metrics, Rescan, hierarchical categories, reused / uncategorized
• FSE hub blocks — List, Categories, Count, Card
• Categories nav: nested terms collapse by default; visitors expand them and the browser remembers
• Preview count per category on the All view + optional pretty category URLs ( /hub-page/term-slug/ )
• Category SEO title / description / image fields; filled SEO title is used as-is (no site-name suffix); pretty URLs use a category canonical
• Drag-and-drop category order on FAQ → FAQ Categories — same order in admin lists, Dashboard, and front-end List / Categories blocks
• Polylang — categories follow the language of the page that owns the FAQ block
• Setup wizard for registry post type and taxonomy slugs
• Convert to FAQ toolbar and Transform to → 4WP FAQ (Accordion, Details, List, heading + paragraph — one or many); default Accordion template on insert
• AI Assistant — WordPress AI Client / Connectors; Generate with AI on FAQ category edit (description + titles + meta). Settings → AI is always visible; markup stays off until a connector is available and Allow predefined field markup is on

AI Assistant

Generation uses the WordPress AI Client . Configure a text-generation connector under Settings → Connectors . FAQ → Settings always shows an AI card; Allow predefined field markup stays disabled until a connector is available.

1. 09Complete registry setup so FAQ categories exist.
2. 10Open Settings → Connectors and finish a connector for text generation.
3. 11Under FAQ → Settings → AI , turn on Allow predefined field markup .
4. 12Edit a category on FAQ → Categories . Generate with AI fills Description , Display title , SEO title , and SEO description from the category name and questions in that term.
5. 13Review, Apply (or Apply all), then Update . Nothing is saved until you update the term.

The plugin does not ship API keys and does not call a model until a connector is configured. Which remote service receives the prompt depends on the connector the administrator selected.

Development

JavaScript and CSS are built with @wordpress/scripts . Human-readable source ( src/ , webpack.config.js , package.json ) is in the public GitHub repository — not in the distributed ZIP.

From a clone:

1. 14cd into the plugin directory
2. 15npm install
3. 16npm run build — compiles block, admin, and setup apps into build/

External services

This plugin optionally sends prompts through the WordPress AI Client when an administrator configures a connector under Settings → Connectors and runs Generate with AI on a FAQ category.

WordPress AI Client / Connectors (optional)

The plugin sends a prompt (site name, category name, question titles in that category, and current field values) through wp_ai_client_prompt() . The WordPress AI Client routes that prompt to the connector the administrator selected. This plugin does not call model vendors directly; which remote service receives the prompt depends on that connector. No visitor or front-end user data is sent. Nothing is generated until a connector is configured and Allow predefined field markup is on.