Modernizing color schemes, upgrade script, theme.json filter#200
Merged
kimcoleman merged 72 commits intomemberlite-7-0from Feb 4, 2026
Merged
Modernizing color schemes, upgrade script, theme.json filter#200kimcoleman merged 72 commits intomemberlite-7-0from
kimcoleman merged 72 commits intomemberlite-7-0from
Conversation
…ntrols via the helper method
…ake the register function easier to manage
…r and some comments to functions that were missing any
…nto custom panels, re-organizing where settings live after feedback
…posts and blog separate setting inherits pages setting
… filters intact - work in progress
…t to get too lost in the rabbit hole
… code with functions
…theme variation color schemes and separate legacy. Too many colors in legacy which can make styling tougher.
…olor scheme settings themselves are not saving the value...
…eir values preserved and the new color scheme setting will read 'leagacy' on it
…ew color scheme setting
… web prefixes, incorrect values, redundant px etc.
…tylesheet. Also added fixes mostly for headings that wasn't in the theme.json, need to organize keys better...
Working toward simplified color schemes and better theme.json integration
kimcoleman
changed the title
RachelRVasquez
added a commit
to RachelRVasquez/memberlite
that referenced
this pull request
Mar 12, 2026
…rstudios#200) * labeling tweaks * remove the need to use the translate function when adding settings/controls via the helper method * separated all those settings and controls into their own helpers to make the register function easier to manage * resolved issue with missing color settings, need to update them to use helpers * put back missing color settings, updated helper * wordpress formatting * colors needed a little organizing too * Fixes based on co-pilot's PR review, added a stylesheet for customizer and some comments to functions that were missing any * new helpers for new sections in customizer, move some core sections into custom panels, re-organizing where settings live after feedback * panels/sections properly ordered via priority * colors in the correct order, a little styling * Wording tweaks; moving some settings around; Adding columns ratio to posts and blog separate setting inherits pages setting * Spaces > Tabs * Replacing webfonts with latin-extended versions for broader language support * Spaces > Tabs * Cleanup of line indentation * Reordering page settings * creating variables and converting arrays into functions while keeping filters intact - work in progress * breaking stuff * pause here before contemplating refactoring to class based, don't want to get too lost in the rabbit hole * commit before switching branches * resolved undefined error I was getting, cleaned up color/color scheme code with functions * Decided to create a new default based on the 4.6 one so we can group theme variation color schemes and separate legacy. Too many colors in legacy which can make styling tougher. * adding in hook I removed, thinking about how to call schemes from customizer file * slowly updating customizer js to keep old color scheme working * colors are saving on an individual level (overrides) for legacy but color scheme settings themselves are not saving the value... * migration function added so those on legacy color schemes can have their values preserved and the new color scheme setting will read 'leagacy' on it * kind of works, a bit funky * trying a different approach to color scheme handling, testing * removing old stuff * looks like it's working, needs regression testing * try adding a new color scheme as an example * only show existing dark mode setting if value is detected, we want to deprecate/replace this in the future * remove theme support for color palette, we don't need it * add styles to the editor stylesheet for fonts, update theme.json so buttons use body font, not heading font * adjust button styles a bit, added a pmpro setting to customizer to override pmpro colors with customizer colors * show pmpro color overrides in live preview * commit before I start breaking things while fixing default colors/overrides in the preview/front-end * formatting and comments * adding documentation for color schemes and presets * more documentation * updated JS to use get_theme_mod to check for legacy, adjusting sync function * commit before switching branches * do we even need to set default for new theme? * trying to fix default value loaded in customizer * corrections * it looks like it's working now PHP wise yay, just tweaking the JS for live preview * we're closer * see if I can get the legacy scheme permanently added as part of the new color scheme setting * working on individual color pickers * looks like it's mostly working on front-end and customizer except the site tagline * stable here before I add new color schemes from Kim * starting to clean up and update comments * cleaned up * bring over Kim's changes in the theme.json * formatting and updated docs * Merging dev * Removing additions to editor.css * initial attempt at documenting project structure * site tagline customizer fix, minor tweak to what CSS var headings use in styles * corrected some minor things that PHP Storm was complaining about, old web prefixes, incorrect values, redundant px etc. * corrected some old prefixes, incorrect values and redundancy in the stylesheet. Also added fixes mostly for headings that wasn't in the theme.json, need to organize keys better... * Fixing an incorrect background color relationship * Reverting some adjustments to a happy medium * Resolving if site title and tagline are hidden * Color scheme tweaking * Fix for header text color properly storing as WP intends * Updating color schemes * Filtering header and body font to theme.json like colors * paces to tabs --------- Co-authored-by: unknown <rachelrvasquez@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
All Submissions:
Changes proposed in this Pull Request:
This pull request focuses on improving color handling and aligning theme settings with
theme.json.theme.json.PROJECT_STRUCTURE.mdCUSTOMIZER.mdcustomizer-controls.jsandcustomizer.jsHow to Test
Other Information
Changelog Entry