RIGHT NOW:
Create a symlinked folder of your local version of fuelux inside of another project (eg: mctheme):
- In fuelux project where you are making fuelux changes:
*
bower link
* This creates a symlink target. - In target project you want to test with fuelux changes:
*
bower link fuelux fuelux-local
* This creates a symlink. You now have local fuelux changes in your other project. * changes will apear in:bower_components/fuelux-local
- When done, remove symlink from target project:
*
bower uninstall fuelux
IDEA FOR FUTURE:
Setup a different grunt serve
to test fuelux changes (grunt serve-fuelux
). This task would replace the links in the example pages to point to your local copy of fuelux.
I have had a few issues pop up in mctheme that I didnt know about until fuelux went live. I think it would be helpful to see what effect the fuelux changes have on mctheme before getting merged into master. This way if there is a styling change to be made in mctheme the pull request can be submitted and ready when fuelux pull request is merged in.