WordPress & Gutenberg FAQ

Yes. Blocks follow WordPress block APIs and work with block themes (FSE) and classic themes that support the Block Editor. They inherit your theme typography and spacing where possible.

Most 4WP plugins are open source (GPL v2+) and free to install. Some are on WordPress.org; others install from GitHub via the 4WP Bundle dashboard. There are no hidden license traps.

Yes. Many engagements start as freelance or part-time WordPress block developer work before a longer hire. Share your GitHub, plugin contributions, and Gutenberg experience when you reach out.

Yes. 4WP Bundle exposes 4wp/v1 REST endpoints; MCP Abilities connects AI agents to WordPress via the Abilities API — both with public source on GitHub.

Most 4WP.dev collaborations are remote-friendly. Specify timezone and availability when you contact us — whether you are applying for a role or hiring for your distributed team.

Yes, under GPL v2+. Fork, adapt, and ship — respect the license and attribution. Many patterns (block wrappers, REST controllers, inventory tables) are reusable starting points for commercial work.

Yes. 4WP.dev offers subcontract and direct hire for block libraries, editor UX, plugin MVPs, and production hardening. Review the plugin portfolio first, then request a conversation.

Yes — Gutenberg developer for hire covers custom blocks, inner blocks, block bindings, editor sidebar tools, and block libraries for agencies. For full agency subcontract scope, see also For Companies.

Yes. Pass the full URL including the path to wp core install –url=. Download and config steps stay the same; only the site URL changes.

No. WordPress needs database credentials in wp-config.php before installation. Without config, WP-CLI cannot connect to MySQL and the install will fail.

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.

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. Plugins are designed as an ecosystem. 4WP Bundle helps manage install, activate, and update when you run several 4WP tools on one site.

Yes, and it is recommended for automated pipelines. The –minor flag restricts updates to the current major branch (e.g. 6.x → 6.x patch), skipping major version jumps.

Yes — common requests include Gutenberg migration, security hardening, test coverage, REST API cleanup, and SOLID restructuring without breaking live sites.

Only when the database named in wp-config.php does not exist yet. On shared hosting the database is often pre-created — then skip this step. On local dev, create it with WP-CLI.

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.

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

No. 4WP plugins are built for the WordPress admin and Block Editor. Install from the plugin catalog, follow the setup guide on each plugin page, and configure options in wp-admin — no PHP or HTML required.

No. Step 4 accepts both git pull and tar -xzf. If the server has Git, pull the branch. If not, upload a tar archive via SFTP and extract it. All other steps are identical.

Basic WordPress knowledge is helpful, but not mandatory.4WP.dev is designed to support progressive growth, helping developers move step by step toward deeper expertise.

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.

Yes. Full Site Editing themes, reusable block patterns, theme.json design systems, and editor-only block addons for agency design systems are core strengths.

Yes — block.json, InnerBlocks, block variations, Interactivity API, block bindings, Query Loop extensions, and editor sidebar plugins appear across the suite (FAQ, Advanced Code, QL Blocks, SEO Helper, MCP Abilities).

Yes. Engagements can run under your agency brand with direct technical communication, clear handoff docs, and Git-based delivery your team can maintain.

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. Output is limited to utility CSS classes and CSS variables. A single generated stylesheet handles responsive rules — no front-end script dependency.

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.

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.

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

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

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

Yes. WP-CLI runs the .sql file against the current database, which typically begins with DROP TABLE IF EXISTS statements for each table. The result is a clean replacement of the existing data, not a merge. This is why the export step before import is critical — anything not in the backup file will not exist after the import.

You can start by exploring the content, joining discussions, and following the learning paths.4WP.dev grows through active participation and shared experience.

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.

Audit open-source repos on GitHub, read architecture docs, inspect release cadence on WordPress.org, and review plugin singles on 4wp.dev — all public proof of how code is structured and shipped.

Start with the plugin documentation on 4wp.dev, then contact 4WP.dev for guided setup or a small configuration adjustment if you need hands-on help.

Use the Contacts popup on this page or visit Contacts. Share role scope, stack (Gutenberg, REST, WooCommerce, etc.), and timeline. Review the open-source portfolio first to see production code quality.

Find the plugin on 4wp.dev/plugin or WordPress.org, click Install, activate under Plugins, then open the plugin settings or insert its block in the editor. Each plugin page includes step-by-step instructions.

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.

Run grep 'siteurl' backup.sql | head -5 before importing. The siteurl value in the dump shows which site and domain the backup came from. If it shows a localhost or staging URL, you will need to run wp search-replace after the import to fix all domain references.

Run wp plugin update –all –dry-run. This shows which plugins have updates available and what versions they would move to, without making any changes.

Share scope, timeline, and stack via Contacts or the For Companies CTA. Include links to reference sites or repos for faster estimation.

Study plugin singles under /plugin/, clone repos, and follow guides on hooks, blocks, inner blocks, Interactivity API, and block bindings. Each plugin is a case study — not a toy demo.

You see real code quality, commit history, documentation habits, and production releases before signing — not just a CV or sales deck.

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.

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.

Content is anchored in shipped plugins — real settings screens, edge cases, release history, and SEO/GSC workflows. You learn from code that runs in production, not isolated snippets.

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.