How timezhero/acf-icon-picker works
File structure
• composer.json: makes the plugin installable via Composer.
• assets/
• screenshots/: example UI screenshot.
README for additional insights
• Mentions integration patterns (Sage/Bedrock filter overrides).
a. Main components
• WordPress Core
• ACF Plugin
– Assets (CSS/JS, Images)
• External Systems: GitHub/Composer repository (for installation)
b. Relationships and data flows
2. When a user edits a post/page and opens an ACF field group, ACF renders the custom field UI by loading the plugin’s CSS/JS assets.
6. Composer/GitHub only come into play at development/deployment time (installation).
c. Architectural patterns / design principles
– Separation of concerns:
• PHP backend for registering and loading field code
• Static assets for admin UI experience
• Configuration via Composer or WP filters
d. Key technologies & libraries
• PHP 7+ (WordPress plugin API)
• ACF 5+ (field registration hooks)
• CSS (Tailwind-ish input.css)
• Vanilla JS (assets/js/input.js)
• Composer package management
Elements
• From plugin bootstrap → ACF hooks
• From browser (admin) → JS/CSS assets → field UI
• From field UI → DB (saving meta) → get_field() → front-end render
• Core WP/ACF in gray
• Assets (CSS/JS/img) in green
• External install mechanisms in orange