CFWD Feedback / Updates

[bd-viget]

Summary

This PR incorporates some of the discoveries found in the CFWD Project. In summary:

• Notes/Comments/Instructions
• Navigation Container Editor Styles
• Post Excerpt Block Support in ACF Blocks Toolkit
• Fixes Duplicate Admin Notice
• Formats theme.json file
• Automates colors for WordPress
• Adds WP Columns and Mobile Menu Breakpoints
• Moves some of the dev files into src folder.
• Updates ACF to latest version
• Updates NPM Packages to latest
• Restores CTA and Image/Text Patterns
• Adds Default templates for Post Archive and Singular

Issues

• WP column breakpoint 751px #147
• Adding options for custom btn icons #124

Testing Instructions

N/A

Screenshots

N/A

[nathan-schmidt-viget]

Looks great! Some really nice update.
One thought with the minifying theme.json if you have a different view, let me know.

[nathan-schmidt-viget]

Glad you updated this as well!

[nathan-schmidt-viget]

Dang this is cool! Did you build this from scratch or find a demo?!

[bd-viget]

Mostly Stack Overflow 🤣

[nathan-schmidt-viget]

😅 good catch

[nathan-schmidt-viget]

The reason I was minifying this is because it saves some file size but more importantly it made it hard to edit the file directly, as any edit should be done in the JS file.

[bd-viget]

Yeah, I think we just need to make sure that's clear from the README/Documentation side, however, I think there are a few good reasons to have it formatted:

• Once the project is handed off, the client may not have the ability to use the build tools, or understand how to manage this file with the provided JS parts.
• Debugging can be difficult, and this makes it easier to determine if styles are coming from theme.json or somewhere else (in a CSS file). It can also be useful to confirm settings are stored as they are expected to be.

[nathan-schmidt-viget]

Good point with the client having the option to edit it post hand off. I like it!