Removes some default customizer fields we never use on projects #377
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DESCRIPTION
Removes some sections and panels from the Customizer that we generally don't use.
During training, I always run through the Customizer but always gloss over a lot of the existing/default Customizer sections with "you can do this here, but it's not the best."
I don't think I've ever known anybody to manage menus or widgets via the Customizer.
For the most part, we don't use a lot of the Customizer features or settings and having so many of them by default just creates confusion for the user. We tend to stick to Site Options and Site Identity, and I can't recall a time where we used Color, Background Image, or (gasp) Additional CSS.
Of course, these could always be added back on a per-project basis by removing the line commenting them out.
SCREENSHOTS
Before:
After:
OTHER
STEPS TO VERIFY
Checkout the branch and open up the customizer.