Frequently asked questions
Clear answers for developers and site owners.
Start here for the practical boundaries around the toolkit, technical requirements, licences and project responsibilities.
What is PorterWP?
PorterWP is a developer toolkit for custom WordPress block themes. It reads project configuration and PHP from a theme, then connects that project structure to native WordPress APIs.
Is PorterWP a page builder or a theme?
No. PorterWP does not provide a ready-made design or visual page-building system. It works with a custom block theme created for the project. WordPress and that theme control the editor and frontend experience.
Why has my developer asked me to purchase it?
Your developer has chosen PorterWP as part of the site’s technical foundation. The production site requires an active licence for its domain. Before purchasing, agree who will own the account, manage activation and handle updates.
How many licences does a project need?
PorterWP requires an active licence for each production domain. Confirm the intended live domain and licence ownership with the project’s developer before checkout.
Does PorterWP require ACF Pro?
ACF Pro is required for PorterWP features that depend on its Pro APIs. The current starter uses ACF Pro 6.6 or newer for ACF Blocks v3. If those APIs are unavailable, PorterWP disables the ACF-backed features while unrelated configuration, assets and helpers continue to load.
Which WordPress and PHP versions are supported?
PorterWP 1.4.95 requires WordPress 6.4 or newer and PHP 8.2 or newer. It is tested up to WordPress 7.0.3.
What can developers configure?
A PorterWP theme can describe post types, taxonomies, ACF option pages, block locations, block styles, assets, theme supports and PHP includes. Premium tools also support public filters connected to core Query Loops.
Does PorterWP replace project-specific PHP?
No. Configuration handles repeatable structure. PHP remains the right place for business rules, integrations and theme behaviour unique to the project.
Where should a developer start?
Begin with the current theme skeleton, review every file under porter/config, then follow the PorterWP documentation.
Who supports my custom website?
PorterWP support covers documented use of the toolkit, suspected PorterWP defects, documentation, and licence or activation questions. Your developer remains responsible for the bespoke theme, frontend code, project integrations, third-party services and server administration. Read the Support Policy for details.
Where can I review recent changes?
The release notes record compatibility, security, performance, fixes and developer-facing changes for current PorterWP versions.
Where are the licence terms?
The existing contractual terms are published separately on the Licence page. The marketing guidance on this site does not replace those terms.
Need the technical detail?
The documentation covers setup, theme configuration, blocks, filters, helpers and the current release notes.