WordPress / WooCommerce / ACF Developer to Fix Gutenberg Page Editing keep Product Templates

# WordPress / WooCommerce / ACF Developer Needed to Fix Gutenberg Page Editing While Preserving Product Templates We need an experienced WordPress developer to help fix and improve the editing experience on **WEBSITE.com**, a WordPress + WooCommerce site hosted on **Kinsta**. The site uses a custom theme called **ACF2022 and is limited**, WooCommerce products for training courses, and ACF / `acf-json` for custom blocks and product/course templates. The current issue is that normal WordPress Pages are restricted by the custom theme and ACF block setup. We want Pages to be editable with a full Gutenberg page design experience while keeping the existing WooCommerce product/course templates intact. ## Project Goal Enable full Gutenberg editing for WordPress **Pages** so we can build and edit modern full-page layouts, while preserving the current ACF/WooCommerce product templates used for course pages. The product/course pages should continue using the existing product template and ACF fields. We do **not** want to break the WooCommerce course catalog, product layout, checkout, course fields, or product category templates. ## Current Site Setup * WordPress site hosted on Kinsta * WooCommerce used for course/product pages * Custom theme: `CUSTOM USING ACF` * Theme uses ACF and `acf-json` * Custom ACF Gutenberg blocks are registered in theme PHP files * Page templates include files such as: * `page.php` * `page-classic.php` * `functions.php` * `inc/theme-init.php` * `inc/theme-acf.php` * `inc/theme-setup.php` * ACF block render files are located under: * `template-parts/blocks/` * Example block issue: * The editor shows a block called `herolarge` * The theme appears to register a Hero block using a render file like: * `template-parts/blocks/hero/hero.php` * We need to identify whether `herolarge` is an old saved block name, ACF JSON block, or legacy registration issue. ## What Needs to Be Fixed The developer should: 1. Review the current theme structure and ACF block registration. 2. Identify what is limiting Gutenberg editing on Pages. Particularly HOME PAGE 3. Enable full Gutenberg block editing for WordPress Pages. 4. Keep WooCommerce product/course templates working as they are. 5. Avoid forcing Gutenberg changes onto WooCommerce products unless necessary. 6. Confirm that regular WordPress core blocks can be used on Pages: * Group * Columns * Cover * Media & Text * Buttons * Query Loop * Reusable blocks / patterns if supported 7. Confirm that existing ACF blocks still work. 8. Investigate the `herolarge` / Hero block issue. 9. Fix or alias legacy ACF block names if needed so older pages do not break. 10. Ensure changes are made safely on Kinsta staging before production. ## Likely Technical Work The solution may involve: * Reviewing `inc/theme-acf.php` * Reviewing ACF JSON field groups * Reviewing `allowed_block_types_all` or similar block restriction filters * Reviewing `use_block_editor_for_post_type` * Reviewing `theme-setup.php` for Gutenberg support * Reviewing page templates and block rendering * Adding or modifying theme support for: * `align-wide` * `responsive-embeds` * `editor-styles` * Ensuring Pages use the Gutenberg editor fully * Keeping WooCommerce `product` post type behavior unchanged * Possibly registering a legacy ACF block alias for `herolarge` if existing pages depend on it ## Important Requirement The developer must **not break WooCommerce course/product pages**. The goal is: * Pages = full Gutenberg design control * Products / Courses = keep existing ACF/WooCommerce product template * Product categories / course catalog = keep existing layout * Header/footer/navigation = do not rebuild unless required ## Deliverables Please provide: 1. A short review of what is currently restricting page editing. 2. A staging-site fix. 3. A list of files changed. 4. A brief explanation of the solution. 5. Confirmation that: * Pages can use normal Gutenberg blocks * Existing ACF blocks still work * WooCommerce product/course templates still work * Existing course/product pages are not broken 6. Recommended long-term cleanup if needed. ## Preferred Experience Please apply only if you have strong experience with: * WordPress custom themes * Gutenberg / Block Editor * Advanced Custom Fields Pro * ACF Blocks * `acf-json` * WooCommerce templates * Kinsta hosting / staging workflow * PHP theme development * Debugging legacy custom themes Experience with products in WooCommerce catalog sites is a plus. ## How to Apply In your proposal, please include: 1. Examples of WordPress sites where you fixed Gutenberg or ACF block issues. 2. Your experience with ACF Blocks and `acf-json`. 3. Your approach to enabling Gutenberg for Pages while preserving WooCommerce product templates. 4. Your estimated time to review and fix the issue. 5. Whether you are comfortable working first on Kinsta staging. We are looking for a careful developer who can fix the theme without rebuilding the entire site. Can create a DEVELOPMENT INSTANCE on Kinsta.com and copy production to let you work with site. The PHP was written in 2022and is restrictive in 2026. Pages are limited, but the product templates display well in the ACF PHP 2022 templates. PAGE DESIGN is what needs to enable the full Gutenberg editor to enhance the site Will send full URL once we engage.