>These aren’t just best practices — they’re practical steps for maintaining quality and scaling your code as your project grows.
AI? These aren't just X, but Y! Plus an em-dash.
Not illegitimate, article seems well laid out. Just interesting to see this in the wild. I've seen this construction in an increasing number of official statements.
What I see (and use myself) is enabling the classic editor, using Advanced Custom Fields Pro with a Flexible Layout. Then implementing a module system for use across different post types and pages. Usually built within a custom theme. Otherwise, I also see page builders such as Elementor & Divi.
I do. I was not into WordPress until recently. Gutenberg has been very easy to get started versus writing a lot PHP. While there are still annoyances, I have managed to work around. Maybe my projects have not been that complicated, but I feel like the Gutenberg team is heading the right way.
>These aren’t just best practices — they’re practical steps for maintaining quality and scaling your code as your project grows.
AI? These aren't just X, but Y! Plus an em-dash.
Not illegitimate, article seems well laid out. Just interesting to see this in the wild. I've seen this construction in an increasing number of official statements.
Do many people use Gutenberg block themes?
What I see (and use myself) is enabling the classic editor, using Advanced Custom Fields Pro with a Flexible Layout. Then implementing a module system for use across different post types and pages. Usually built within a custom theme. Otherwise, I also see page builders such as Elementor & Divi.
Yep, this is best approach imo.
I do. I was not into WordPress until recently. Gutenberg has been very easy to get started versus writing a lot PHP. While there are still annoyances, I have managed to work around. Maybe my projects have not been that complicated, but I feel like the Gutenberg team is heading the right way.