Quick summary
A WordPress rebuild note about taking a live-site crawl and turning it into a custom theme architecture with reusable Gutenberg blocks, custom post types, and a Vite-based asset pipeline.
The problem
The site needed a rebuild path that preserved imported content but moved it into an editable WordPress structure instead of freezing the whole design into one-off hardcoded templates.
What I checked
- Crawled live-site content and page inventory
- Theme architecture needed for reusable sections
- Custom post type and taxonomy requirements
- Dynamic block opportunities for page sections and galleries
- Frontend asset build and deployment constraints
What I changed
- Built a custom WordPress theme shell with PHP templates, shared components, and Vite-managed frontend assets
- Registered custom post types and taxonomies for offers, projects, reviews, jobs, and imported content organization
- Added dynamic Gutenberg blocks for page heroes, breadcrumbs, offers, brands, galleries, maps, and reviews
- Set up crawl, import, seed, and modernization scripts so imported content could be moved into the new structure
- Kept the homepage template-part driven and interior pages block-based so the site stayed easier to evolve
Result
The rebuild created a more maintainable WordPress content model where reusable sections, imported media, and future page changes could live inside the theme instead of scattered hardcoded layouts.
Where this fix usually leads next
This kind of work usually connects back to WordPress Support, Landing Pages and Technical SEO so the fix note can lead into a clearer support path instead of staying as an isolated one-off task.
What I'd watch next
- Whether imported media and crawl-generated content stay aligned with the new content model
- Whether dynamic block render callbacks need regression checks after WordPress updates
- Whether the Vite manifest and built assets are refreshed consistently before deployment