Convert Tailwind/ACF based WordPress to use create-guten-block & other NPM functions

We have built a custom WordPress theme with clean code, but I would like to modify the structure to depend on the npm library create-guten-block and utilize several available technologies: My goal is to have a good example and base to build our next site off of - not to convert the entire site, because of this - we will start with only 2 guten blocks, header and footer. 1: Migrate 2 custom guten blocks to create-guten-block -- Currently, all custom guten blocks are created using ACF blocks, but I would like to migrate a couple to create-guten-block 2: Migrate header and footer to be using templates and template parts as described in Full site editing: [login to view URL] 3: Using create-guten-blocks [login to view URL] and [login to view URL] and a similar structure for template & template parts - all tailwind styles should be using @apply within nested SASS. - make sure to apply both frontend and backend styling as it is currently. 4: Replace ACF Fields with native WordPress fields OR Merge ACF Fields into our new create-guten-blocks version. 5: The guten blocks and template-parts should only use a wrapper div with a class like "hero", "footer" or "masthead" - and as few classes as possible on inner elements, as we can style them by targetting within nested classes in the components SCSS file. 6: FOR DEVELOPMENT: Enable Livereload with tailwind/sass being watched and rendered in real time as code changes are made to tailwind config or any scss file. 7: For PRODUCTION ONLY: Enable Auto-prefixing, purge and minify in Tailwind - and output 1 CSS file that is as compact as possible. (Avoid these operations in development to speed up processing for live reload mentioned in #6) Before getting started - we should have a live zoom meeting to review the current code and make sure that everything makes sense. We will also work together to getting a live copy of the site using [login to view URL] and GitHub, and then you will fork the code and build in an isolated environment. Once complete, I would like to have another zoom meeting where we discuss/review your implementation together so that I can fully understand your approach.