Technical Requirements
One of the initial projects involves developing a custom Travel Tips template using ACF Pro.
The template will follow a modular architecture:
- ACF Pro with Local JSON
- Fixed Core Sections shared across all Travel Tips articles
- An expandable Flexible Content system for category-specific sections
- Reusable ACF layouts/components
- Dynamic headings and content fields
- Drag-and-drop ordering of flexible sections
- Category-based availability of relevant layouts
- Optional fields must not produce empty HTML wrappers or unnecessary spacing
- Responsive image handling using WordPress native image functions
- Semantic HTML and proper heading hierarchy
- Lightweight, performance-focused frontend
- Clean and maintainable PHP
- No hard-coded module headings or category-specific sections inside the template
- Architecture should make it easy to add new categories and layouts in the future without modifying the Core template
Performance & Code Quality
The developer should understand:
- ACF Flexible Content best practices
- Efficient
get_field()/get_sub_field()usage - WordPress native responsive images
- Conditional rendering of optional content
- Avoiding unnecessary DOM elements and database queries
- WordPress template hierarchy
- Maintainable, modular PHP architecture
The goal is to build the Core structure once and keep it stable, while allowing the Flexible Content system to expand as new content requirements arise.
A detailed technical specification and example ACF structure will be provided to the shortlisted developer.
Trial Project
We may begin with a small paid test project to evaluate code quality, communication, architecture and attention to WordPress/ACF best practices before moving to ongoing development work.
