No. Elementor is optional. The Gutenberg block and [forwp_booking] shortcode work on any block theme without page builders.

No. Clinic Cards is a third-party service by Cliniccards Corp. 4WP Booking is an independent product by 4wp.dev that communicates with Clinic Cards via their documented API.

Clinic Cards is a cloud CRM for dental clinics — interactive schedule, patient cards, visual treatment plans, finances, inventory, online booking, and eHealth integration. 4WP Booking connects your WordPress site to their public API.

When a visitor submits the booking form: name, phone, email, optional comment, selected service, date, and time. Data is sent only on submit, not during browsing.

In WordPress options on your server. The key is never included in front-end HTML or JavaScript — all API requests are server-side HTTPS calls to cliniccards.com/api.

Google Calendar and Calendly are on the roadmap. The plugin uses a pluggable provider architecture — Clinic Cards is the first live connector.

No. Each 4WP plugin works standalone. Bundle is recommended when you run several 4WP plugins and want one dashboard, catalog sync with GitHub, and shared addon blocks in the editor.

Go to 4WP Bundle → Addons, check or uncheck each addon, and click Save. Disabled addons are not registered on init, so they disappear from the block inserter.

Download the zip from github.com/4wpdev/4wp-bundle, upload via Plugins → Add New, or use the Bundle dashboard to install sibling plugins from the catalog. Activate under Plugins.

Under 4WP Bundle → Blocks, the UI lists every installed 4wp-* plugin and compares versions against the remote plugins.json manifest from GitHub. You can install missing plugins via download URL, activate or deactivate, update when a newer release exists, and open README or documentation links.

Yes — GPL v2 or later. Source on GitHub, maintained by 4WP.dev. Not on WordPress.org yet; install from GitHub or via the ecosystem dashboard.

WordPress 5.0 or higher and PHP 7.4+. When installing from GitHub source, run npm install && npm run build to compile block addons. Rename the folder to 4wp-bundle if GitHub adds a -main suffix.

Three addons ship with Bundle: Show More (collapsible content), Swipe Carousel (InnerBlocks + Swiper), and Video Lightbox (trigger opens video overlay). They register only when enabled.

4WP Bundle is the core hub plugin for the 4WP open-source suite. It provides a React-powered wp-admin dashboard to install, activate, update, and manage sibling 4wp-* plugins, plus optional built-in Gutenberg block addons (Show More, Swipe Carousel, Video Lightbox).

GET /wp-json/4wp/v1/blocks · POST …/plugin-install · POST …/block-toggle · POST …/plugin-update — each requires appropriate WordPress capabilities (manage_options, install_plugins, etc.).

The dashboard fetches plugins.json from the 4wpdev GitHub org — slugs, versions, repository URLs, and optional GitHub Releases download URLs. Documentation links point to 4wp.dev/plugin/{slug}/.

Yes, drafts are also scanned and shown as sources. Status is visible in the “Used in” list on FAQ Cards when sources are enabled.

List and Categories share include/exclude even when they sit in different columns. Two categories on the List → the same two in the nav. More on the nav → the List includes those too. Empty include on one side inherits the other; empty on both means all categories. All categories always shows that synced set, not a different universe of questions.

It scans all posts looking for forwp/faq wrapper. Inside, it takes Accordion items/Details blocks and extracts: question, answer, post_id, post_type, and permalink.

Complete registry setup, run a rescan, then in the Site Editor add 4WP FAQ Categories (sidebar) and 4WP FAQ List (main column). Optionally add a core Search block and turn on 4WP FAQ → Filter 4WP FAQ List. Questions stay on the real pages; the hub only reads the registry.

Add core Accordion (or item) → Click “Convert to FAQ” → Plugin wraps it in forwp/faq without changing appearance.

Reuse today means the hub: the same registry questions render on a glossary page via 4WP FAQ List. Auto-inserting a question into a new Accordion is still on the roadmap.

Potential next stage: click tracking. It gives understanding of which questions are actually “live”.

• What is 4WP.dev? Platform for WordPress developers with docs, courses, patterns.
• How do I start learning? Start with Knowledge Base, pick a path, move to courses.
• Is the content free? Most content is free, some advanced courses may require subscription.

Off by default: filter in place, URL unchanged. On: one extra path segment after the current page, e.g. /faq/for-companies/. Opening that URL directly shows only that category. The “All categories” link returns to the host page.

• 4WP FAQ List (forwp/faq-list) — grouped by category or a single list. Include/exclude taxonomy terms.
• 4WP FAQ Card (forwp/faq-card) — inner template of the List: accordion or heading + answer. Optional “Used in” source links and post-type label.
• 4WP FAQ Categories (forwp/faq-categories) — vertical or horizontal nav. All categories is a replaceable label that still shows the full synced list.

A smart wrapper around WordPress core Accordion that adds intelligence without breaking design. It adds Schema JSON-LD, an optional question registry, and FSE hub blocks (List, Card, Categories) while working on top of existing content with zero duplication.

In the FAQ-CPT page metabox, there is a JSON-LD preview. Copy it with one click. It represents what the plugin generates on the frontend.

Because the source of truth is your actual content pages. We do not create duplicates – we read facts from real pages. This gives transparent insight into where questions live, in which posts, and in what versions.

Not yet. Apple Health has no web OAuth flow. A future release may add an iOS bridge or third-party aggregator through the provider registry.

No. Samples are stored in your WordPress database on your server. The plugin does not phone home to 4wp.dev.

Google OAuth for authorization and the Google Fitness API for activity datasets — steps, distance, calories, and exercise sessions — only after the user consents and an admin saves valid OAuth credentials.

A WordPress plugin that lets logged-in users connect Google Health / Fitness data — with admin charts, Gutenberg metric blocks, REST endpoints, and a provider registry for future sources.

Clone or download from GitHub. Part of the 4WP Bundle ecosystem.

Data belongs to the WordPress user who connected Google Health. Trainers and administrators need explicit capabilities to use the customer picker and health admin screens.

Yes. Choose the custom SVG option in the icon library when Lucide does not include your mark — useful for logos and client-specific assets.

Yes. Toolbar controls add icons to Button, Heading, Paragraph, List, and Quote blocks in addition to the standalone 4WP Icon block.

No. Icons render as inline SVG on the server. Visitors do not load a Lucide React runtime — keeping pages lightweight.

A Gutenberg block plugin that brings the Lucide icon set (1000+ icons) into WordPress with a searchable picker, custom SVG support, links, and inline icons for selected core blocks.

Source and releases are on GitHub. It powers iconography across 4WP.dev and ships as part of the 4WP Bundle ecosystem.

Lucide — consistent stroke-based icons used across the 4WP.dev site and plugin landings. The picker exposes the full generated catalog, not just icons already used in the editor bundle.

No. Templates keep base slugs like header. You create locale-specific template parts (header-en, footer-de, etc.) or map custom slugs in the admin table.

Swapping runs on the front end (and is suspended during admin/REST). Editors still manage all parts in the Site Editor; admin tabs help map, clone, and audit coverage.

Version 0.2 adds pattern language scope and filters the block pattern inserter via REST so editors see patterns relevant to the active language.

It resolves base FSE template part slugs (header, footer, and custom parts) to language-specific versions on the front end, based on the active Polylang or WPML locale.

The resolver falls back to the base slug so the site keeps working. The Design System tab highlights missing variants so you can clone them in one click.

Polylang and WPML via built-in providers. The plugin auto-detects which one is active and reads the current language slug from that stack.

MVP includes ICS feed export and per-item “Add to Google Calendar” links. Two-way Google OAuth sync is on the roadmap — see GOOGLE-SETUP.md in the repository for current setup notes.

No. Planning only — no automated actions. 4WP Planner helps you organize work and due dates; it does not post to WordPress, social networks, or deploy plugins on your behalf.

Not yet. Install from the GitHub repository. An official directory listing has not been submitted.

No — early-stage development. The plugin is actively evolving (currently v0.3.0). APIs, admin screens, and calendar sync may change between releases. Use on staging or internal installs until we publish a stable roadmap.

Yes — namespace fwpp/v1 with routes for projects, plans, items, calendars, insights, and meta. Useful for future dashboards or internal tooling; treat endpoints as unstable during early development.

Items support typed work units — articles, plugin releases, social posts, tasks, and related studio work — grouped under projects and optional weekly, monthly, or quarterly plans.

An internal WordPress admin tool for planning content, plugin releases, and calendar-driven work across projects, plans, and items. It is designed for studio workflows at 4WP.dev — not as a generic project-management SaaS replacement.

Yes. Presets use named utility classes; arbitrary values use a has-forwp-*-custom class with a CSS variable (for example --forwp-padding-top-mobile: 150px) instead of inline styles.

No. The plugin extends blocks that already support spacing, typography, and alignment — such as Heading, Paragraph, Group, and List — via sidebar controls.

No. Output is limited to utility CSS classes and CSS variables. A single generated stylesheet handles responsive rules — no front-end script dependency.

Spacing and font-size presets are read from the active theme’s theme.json. Breakpoints can be defined in settings.custom.breakpoints; when present, they override plugin defaults and lock conflicting admin fields.

Not yet. The plugin has not been submitted to the official WordPress.org directory. Install and review the source from the GitHub repository.

Block content remains intact. Responsive utility classes and variables stop applying, so layouts may look different — but no block markup is destroyed. This is by design for a safe fallback.

4WP Responsive adds Desktop, Tablet, and Mobile controls for spacing, visibility, font-size, and text alignment on core Gutenberg blocks — through the block inspector, without custom blocks.

By default under wp-content/uploads/4wp-responsive/, cached with a content hash. You can override the storage path in Settings → 4WP Responsive if your deployment requires a fixed location.