Meeting
Web Process Consulting | Recurring
Gist
Chris walked Gavin and Kimberly through technical concepts for automating Local Jungle's WordPress theme: theme.JSON color variables, custom post types with ACF fields, and dynamically pulled global data (phone numbers, addresses) instead of manual duplicate edits across header/footer. They discussed automating coupon cards, page-speed concerns from adding a second template, and using a parent/child theme structure instead of building a separate carbon-copy template. Chris recommended pausing development on template two until the current theme's blocks are audited and automated, and Gavin agreed to audit the site and send a Google Doc breakdown before end of week.
Distilled from the transcript by claude-sonnet-5 · Jul 25
What came out of it
Decisions3
- Pause developer work on building template number two until the current theme is optimized
- Use a parent theme with toggleable layout variations rather than maintaining two separate carbon-copy templates
- Move global site data (phone, address, hours) into a theme options panel pulled dynamically rather than hardcoded in multiple spots
Risks and blockers4
- Page speed insights scores have dropped significantly across sites with no known cause, and adding more custom code could worsen this
- Maintaining two nearly-identical templates in parallel doubles maintenance work for every future change
- Existing coupon plugin is finicky and has broken the entire site before
- Google Maps zoom/sizing is a manual nuance per client that resists automation
Open questions3
- Whether the data table for global service/competitor info should live in a theme options panel or be built as a shared Gutenberg block
- Exactly which fields and blocks should be automated via custom post types vs. Gutenberg-native blocks
- How to handle the specials/deals page vs. homepage coupon card long and short display versions
Next steps5
- ClientAudit the current site template to find duplicated content across pages (phone numbers, addresses, coupons, team members) and document it in a Google Doc
- ClientSend the audit Google Doc to Chris before end of week
- MeProvide a weekly action-item breakdown after each call so Gavin can pass tasks to developers and the internal ClickUp team
- ClientPause the second template's development with the outside developer
- ClientCreate a ClickUp task to track the audit assignment
A record of what was agreed, not a task list — nothing here was scheduled.
From this meeting
No tasks spawned from this meeting.
Notes
No notes on this meeting yet. Use the plus Note button to add one.