New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Customizer Updates #8400
Customizer Updates #8400
Conversation
…ays load util.mediaQuery
For @kball, this is the spec for the configuration. {
"modules": [],
"variables": {}
}
"variables": {
"primary-color": "#ffffff",
"global-flexbox": "true"
} To create a custom build, run: gulp customizer --modules path/to/config.json A ZIP file with the name |
…output flags, and ensure all files print to the correct output directory
…stomizer/config.yml
…ed into $foundation-palette
@kball I've made the final needed changes on my end:
|
…if no color variables are included in the custom build definition
… JSON given is missing the variables key
This is now working & the web interface is live. |
@kball and I are working on some updates to the customizer. The big thing is integrating the build process directly into the foundation-sites Gulpfile. This makes it easier to test various configurations, and easier to test the custom builds with the framework before we deploy a new version.
On the server end, the customizer holds a specific tagged version of the repository, and can generate custom builds by running
gulp customizer --modules path/to/config.json
, whereconfig.json
is a file built from the customizer's form data.The server end is still being worked on (and will probably be closed source).