-
-
Notifications
You must be signed in to change notification settings - Fork 79k
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 - comment w/ differences #9831
Comments
Nice thought but we likely won't be going that in the customizer. That's a job for the changeling and blog post. |
I'm not sure if we understood each other. Changeling and blog post are for differences you have made between v.2.3.2 and v.3.0.0. I was thinking of listing a differences between That is usefull info for presetting customizer when next versions is released. Anyway, thx for your answer. |
I think you can easily do that using any diff tool. |
Not easily if compiler creates multiple changes in .css based on one paramater. i.e. changing Instead of comparing diffs, I just need to have my (unique) presetting of customizer saved for future updates and patches.
|
Yeah baby, that's what I was talking 'bout... http://getbootstrap.com/customize/?id=... It would be nice if that was stated in dosc, rather then mentioned in blog. Still, although this is perfect for short time usage, I think there are two issues:
|
Tweeking and upgrading TWBS is neverending story, therefore new v. and patches are imminent.
Would it be nice for customizer to have at the top of customized bootstrap.css comment w/ differences between default and generated customized version?
/!
** Customised variables ***
*** Typography ***
@font-family-sans-serif Arial,Helvetica,sans-serif
*** Headings ***
@headings-font-weight 700
*** Components ***
Border radius sizes
@border-radius-base 3px
@border-radius-large 4px
@border-radius-small 2px
etc.
*/
This would make customizing next iteration much easier.
Just a thought.
Thx for all great work (& vids you post)
The text was updated successfully, but these errors were encountered: