- Load Evogene CSS only on the flexible template
Enqueue style-evogene.css only when the page uses “Flexible Page (Evogene)” (conditional enqueue).
- Add ACF field instructions for headings
Add instructions/descriptions to the relevant WYSIWYG fields (e.g. “First line becomes H1”, “First line becomes H2”) so editors know how content maps to H1/H2/H3.
- Document heading hierarchy
Create a short doc (e.g. in the theme or as a comment) that lists which section/layout uses H1, H2, or H3 for the Evogene page.
- Introduce H4 where needed
If the design or content has a fourth level (e.g. under partner card titles or in long WYSIWYG blocks), add H4 in the right places and in the helper/templates if necessary.
- Tighten Evogene CSS
Refine spacing, typography, or colors in style-evogene.css to match Figma more closely or improve responsive behavior.
- Test/edge-case for WYSIWYG headings
Handle edge cases when “first paragraph” is missing or content has no <p> (e.g. single line, or content pasted without paragraphs) so H1/H2/H3 still output correctly.
- Testimonial block SEO
Decide if the testimonial block needs a visible or visually hidden heading (e.g. H2 “What partners say”) and add it if yes.
- ACF JSON export
Export the Evogene ACF field group to acf-json (or sync from UI) so the group is in version control and consistent across environments.
- Figma checklist for Evogene
Turn the “how to mark H1/H2/H3 in Figma” steps into a short checklist (or doc) tailored to the Evogene page (which frame = H1, which = H2, etc.) for designers.
- Accessibility/SEO checks
Quick pass: one H1 per page, heading order (no skipped levels), and link/button labels; fix any issues found.You can paste this list (or the numbers you care about) on the next page and say e.g. “Do tasks 1, 2, and 5” or “Do task 1 only.”