Features
A focused toolkit for the parts every custom theme needs.
PorterWP brings project structure, WordPress registration and theme integration into one documented workflow while leaving project-specific decisions in your theme.
CONTENT MODEL
Post types and taxonomies from project configuration
Describe labels, supports, relationships and registration arguments in the theme. PorterWP turns those definitions into native WordPress post types and taxonomies.
- Theme-owned configuration
- WordPress registration arguments
- Optional local ACF field groups
CUSTOM BLOCKS
Component-shaped ACF Blocks v3
The starter groups block metadata, field JSON, PHP rendering, styles and optional JavaScript in one discoverable folder. PorterWP registers the enabled block directories.
- ACF Blocks v3 scaffold
- Local field JSON beside each block
- Unique frontend runtime IDs for repeated blocks
QUERY TOOLS
Scoped Query Loop filtering
Add search, taxonomy, post type, metadata, date, geography and ordering controls to the intended core Query Loop. Signed, route-bound filter schemas protect the public request surface.
- Core Query Loop integration
- Scoped theme helpers for custom rules
- Bounded legacy link compatibility
THEME CONFIGURATION
Assets, support and block controls
Declare public assets, editor assets, script attributes, theme supports, image sizes, block styles, pattern categories and project PHP include paths from the theme.
- Frontend and editor assets
- WordPress theme support
- Core block styles and project controls
PERFORMANCE
Caches with project boundaries
Configuration and Site Editor preview work use bounded caches scoped to the active site and theme. Source changes invalidate the relevant cached data, including valid empty results.
- Site and theme scoped cache keys
- Source-aware invalidation
- Block editor assets limited to editor screens
LIFECYCLE
Helpers for production content
Optional helpers cover scheduled status transitions, rewrite handling, template parts and cache management while respecting site timezone and existing publication states.
- Batched scheduled work
- Guarded status transitions
- Theme helper APIs retained for existing projects
Dependency boundary
Use ACF Pro when the project uses PorterWP ACF features.
The current starter scaffold uses ACF Pro 6.6 or newer for ACF Blocks v3. If required ACF APIs are unavailable, PorterWP disables those ACF-backed features while its unrelated configuration, asset and helper features continue to load.
Current compatibility
A supported baseline for modern WordPress projects.
PorterWP
1.4.95
WordPress minimum
6.4
WordPress tested
7.0.3
PHP minimum
8.2