- Article
- Intermediate
- 2 minutes read
- Reviewed August 4, 2026
- Advanced WordPress and integrations
WordPress functionality can live in a theme, plugin, must-use plugin, external service or independent application.
The decision should follow the responsibility and lifecycle of the feature.
Theme
A theme owns presentation:
- Templates.
- visual styles.
- layout.
- design tokens.
- theme-specific patterns.
- rendering choices.
Content and business functionality that must survive a theme change should not depend entirely on the theme.
Plugin
A plugin owns portable WordPress functionality:
- Custom post types.
- taxonomies.
- settings.
- integrations.
- REST routes.
- blocks with functional meaning.
- workflows.
- data models.
A plugin can still provide frontend templates and styles where the feature requires them.
Must-Use Plugin
A must-use plugin loads automatically and cannot be disabled through the normal plugin screen.
It can fit organization-owned infrastructure, hosting integration and mandatory platform behavior.
It requires explicit deployment and handover because normal activation hooks and administration expectations differ.
External Service
Use an external service when the responsibility needs:
- Independent scaling.
- specialized runtime.
- centralized data across sites.
- isolated security boundary.
- event processing.
- heavy computation.
- independent release cycle.
- non-WordPress clients.
WordPress then integrates through HTTP, queues or webhooks.
External Application
A separate application can provide a complete interactive product while WordPress supplies identity, content, commerce or an entry point.
Define session, API, domain, deployment, monitoring and ownership boundaries clearly.
Decision Questions
Ask:
- Does it survive a theme change?
- Does it need WordPress content and permissions?
- Is the data site-specific or platform-wide?
- Does it require a different runtime?
- Is it synchronous or background work?
- Who deploys and supports it?
- How is it removed or migrated?
- Which failure boundary is acceptable?
Frequently Asked Questions
Can a plugin include React?
Yes. The architectural boundary depends on responsibility, not the frontend library.
Should every heavy task leave WordPress?
No. Measure workload and operational complexity first.
Continue Learning
Previous: The WordPress Abilities API