Victor Ramirez talks about the approach here: https://www.youtube.com/watch?v=3o66SvY9G1k&t=91s
The plan itself was posted on Twitter. It is a bit old, but it sounds like decent approach
Level 1
- Style the editor and core blocks to match the client theme.
- Disable custom colors & fonts to keep the client on brand
- Disable all core blocks your client doesn’t need per post type. Too many options are confusing. (Optional)
Level 2
- Customize the core blocks by adding block styles (think body styles on a car)
- And extend existing functionality
- Example: You don’t need a custom testimonial block. You need a block quote with a custom style and link attribute!
Level 3
- Build Gutenberg block patterns by grouping together core blocks and styling with CSS.
- Pro-tip: also disable columns. They’re too messy & your patterns can cover these.
We still have not created a custom block, installed any plugins, or added dependencies
Level 4
- Build custom blocks via ACF. We are only adding ACF for ease of use. Fields, custom post types, taxonomies, & user roles are all core WP.
- Less time training developers, training users, & maintaining systems (the hardest part!)
- 6-Step Guide To Custom Post Loop Gutenberg Blocks by Joey Farruggio