-
Notifications
You must be signed in to change notification settings - Fork 0
Pulling in Foundation Updates
Since each child theme comes bundled with it's own version of Foundation (courtesy of Bower), it's on individual child theme developers to pull in these updates as needed.
In most cases updates to Foundation are opt-in -- they may add a few variables, or fix a minor bug. If your theme doesn't need the changes, you don't necessarily need to update Foundation right away. If for some reason an update is required we'll be sure to communicate it loud and clear.
Be sure to peruse the release notes and familiarize yourself with changes that have occurred since your current version, and always review the generated scripts and styles and test your theme after pulling in the updates.
When a new release of Foundation is announced, follow these steps to pull it in to your theme:
-
Update
package.json
.{ "name": "your-theme-name", "devDependencies": { "responsive-foundation": "git+ssh://[email protected]:bu-ist/responsive-foundation#X.X.X", }, }
Modify the version tag at the end of the repository path (X.X.X).
-
Run
npm install
. -
Run
grunt build
.
Getting an error on
npm install
? Be sure you're trying to pull in a Foundation update, and not a Framework update. Foundation updates cover static assets, such as SASS and JS files. Framework updates cover parent theme files that your child theme depends on, such as PHP. If the update is made to the Framework - the parent theme - you don't need to do anything. You'll automatically be up to date.
If you get this error (exit code of #69 Agreeing to the Xcode/iOS license requires admin privileges, please re-run as root via sudo.
), you need to open XCode and accept the agreement.
This will bring in updates to the node_modules
directory as well as the generated stylesheets. Review and commit these changes:
"Pulling in Responsive Foundation X.X.X"
In order to see the changes, you'll need to upload the node_modules
directory as well as the generated stylesheets to your development environment.
Nothing, only if your theme is not affected by the change. So peruse the release notes!
Get started
Configuration
Build child themes
- Customizing CSS in a child theme
- Overriding templates in a child theme
- Code patterns
- Code reviews
- Pulling in Foundation Updates
- Merging and Creating a Pull Request
Sass
Javascript
PHP
- Coding Standards
- PHP Constants
- Temp PHP Code Patterns
- PHP Snippets
- How to Use Hooks
- Action Hooks
- Using Action Hooks To Output Markup
- Filter Hooks
Shortcodes
Templates
GitHub
Tasks
Contribute to the framework
- Framework Development and Release Workflows
- Documentation Template
- Testing your changes
- Creating a new release
- Migration Guide
- Needs Documentation
Code Examples
- Adding Content Container Classes
- Adding News Templates
- Adding Script Dependencies
- Changing Available Layouts and Default Layout
- Displaying a Fancy Gallery
- Loading a Custom Build of Modernizr
- Loading Modernizr in the Footer
- Using Action Hooks To Output Markup
- Understanding get_template_part
BU Developer Resources