> Marketplace requirements are another problem. Authors have to keep original Bootstrap CSS and JS files and overwrite them in separate files. It generates unnecessary CSS and JS code.
The reason for this is so when the new dot release of $BASE_FRAMEWORK comes out, you can drop it in. CoreUI looks cool, but:
> I wanted to keep CoreUI as lightweight as is possible, so I decided to remove all the unnecessary Bootstrap components.
I wonder how updating Bootstrap releases is going to work? Clearly the author is going to update manually -- for a while. When he gets bored will the whole thing become unusable because of all the custom surgery?
It's ease to keep it up to date. I added my scss files to bootstrap.scss, so if new version of bootstrap will be released all I need to do is update bootstrap scss file in my project.
I think Domenic's objection is that it sounds like you're going into, for example, _forms.scss and dropping something unnecessary like the styling of the `output` tag.
Are you instead just going into bootstrap.scss and commenting out entire includes?
The former implies a lot of surgery and the latter is definitely more manageable, but could still suffer from the project abandonment he brought up.
In current version I only removed components from bootstrap.scss, but in future version I also want to remove some code from scss files like for example _navbar.scss. Who needs 3 versions of navbar in one project?
But the point & purpose of CoreUI is that all the "unnecessary" theming (his example: Jumbotrons) is deleted. If you copy the new version of Bootstrap's scss files in, you will lose those optimizations -- negating the entire point of CoreUI.
10 comments
[ 3.4 ms ] story [ 27.8 ms ] threadThe reason for this is so when the new dot release of $BASE_FRAMEWORK comes out, you can drop it in. CoreUI looks cool, but:
> I wanted to keep CoreUI as lightweight as is possible, so I decided to remove all the unnecessary Bootstrap components.
I wonder how updating Bootstrap releases is going to work? Clearly the author is going to update manually -- for a while. When he gets bored will the whole thing become unusable because of all the custom surgery?
Are you instead just going into bootstrap.scss and commenting out entire includes?
The former implies a lot of surgery and the latter is definitely more manageable, but could still suffer from the project abandonment he brought up.
All in all I liked what I saw :)