POM Theme for developers

This chapter documents the supported contracts available to a plugin or child theme integrating with POM Theme. It covers public helpers, template syntax, programmatic forms, conditional assets, CSS utilities, and the supported WP-CLI audit command.

Check helper availability when POM Theme is optional. Do not include theme files directly or depend on generated files, private classes, settings storage, or builder serialization.

Start here

1. Supported extension points and compatibility rules
2. Sanitization, escaping, and capability requirements
3. Performance requirements for POM extensions
4. Read POM theme settings safely
5. Work with builder data safely

Public helper references

6. Use color and icon helpers
7. Use image and lazy-loading helpers
8. Use button and pagination helpers
9. Use term and content helpers
10. Evaluate POM permission rules
11. Check compatible integrations
12. Use sidebar and social helpers
13. Load assets only where they are needed

Focused developer topics

14. Create forms programmatically
15. Use POM CSS helpers
16. Use template merge tags
17. Choose a template integration
18. Register plugin-owned content models
19. Regenerate theme assets
20. Understand progressive archives
21. Use supported WP-CLI commands

Compatibility baseline

• Use WordPress hooks and documented POM functions.
• Treat slugs, field names, template identifiers, and setting keys as durable contracts.
• Sanitize incoming data, authorize writes, verify nonces, and escape at output.
• Execute multisite work in the intended blog context.
• Load assets only when the integration renders.
• Provide an explicit fallback when a POM subsystem or third-party integration is unavailable.