Maintain a classic child theme, or move to FSE theme?
-
Hi there,
We maintain a StoreFront child theme for over 7 years now, and were pretty happy with it until now.
Over the years, we’ve added a lot of content to our website : new designs, new pages, products, and translated it in several different languages.
While we started with custom CSS and template parts, much of the new content was built with a page Builder (Elementor, not to name it).
That was a very convenient shortcut at that time, since we had a huge freedom in terms of content design, without the need to call upon a developer.Now that our design identity is mature, but the page builder becomes an obtacle:
- Compatibility issues
- Caching errors
- Performance (huge DOM, too much unnecessary assets loaded)
- Styling harmonization
- Content maintenance
- Bugs
- …
Long story short, we want to get rid of this page builder, and structure our content on long term development tools: custom blocks.
Here is our plan:
- Move away from a single style.css files (fed from well strutured .scss files), to Gutenberg custom blocks.
- Instead of moving to a FSE theme / theme.json, keep our classic theme, and build custom logic to load what’s needed only where needed (what FSE does natively, as far as I understand).
In your opinion, is it the right strategy?
Or building, and maintainting that custom logic is so much work on the long run , so that we should rather already migrate to an FSE theme?
Thank you
- You must be logged in to reply to this topic.