Use of normalize and other libraries

[Serkan Durusoy]

Hi,

Do you think we should be using normalize.css or any other css reset before including Semantic UI? Or does SUI already cover that area?

Also, I'd like to hear about experiences on other complementary css libraries (especially for typography etc) with SUI and I'd be really glad if more experienced SUI users/developers could share some tips.

Perhaps they can make their way into the docs as well.

Thanks

Serkan

[Frankie Bagnardi]

Serkan, this has been brought up before.  Feel encouraged to include your own CSS reset, etc. but Semantic doesn't modify the page in any way except within the scope of its components.  If you don't use the "ui" class anywhere on your page, you won't know it's even there.

[Serkan Durusoy [DNA | encoding the future]]

Hi Frankie,

Thank you for your response.

To clarify this even further, could we say that "if we are going to
stick to SUI all the way, then we don't need any resets at all"?

Also would you recommend including any other css/js library to
complement SUI in other ways?

Thanks
Serkan

[Jack Lukic]

The option for packaged resets are built into 1.0 as well as site wide variables like font size etc.

https://github.com/Semantic-Org/Semantic-UI/blob/css/src/site.less

They are not part of the pre-release (main) dev branch.

Thanks
Serkan

--
You received this message because you are subscribed to the Google Groups "Semantic UI" group.
To unsubscribe from this group and stop receiving emails from it, send an email to semantic-ui+unsubscribe@googlegroups.com.
To post to this group, send email to seman...@googlegroups.com.
Visit this group at http://groups.google.com/group/semantic-ui.
For more options, visit https://groups.google.com/groups/opt_out.

[Serkan Durusoy [DNA | encoding the future]]

Wow! This is great news.

I know you have already announced apr/mar for 1.0 release, but do you
think you can propose a timeframe for early access to these?

[Jack Lukic]

They are ready to be used today, and im using this branch in my consulting work. 

The caveats are:

-many components still need to be converted to variabled less

-theming is undocumented but you might gather an understanding from conversations on github issues

-the folder structure might shift around. 

Currently user overrides are in /user/ which will be overwritten if you use a package updater like bower, this will most likely be in a directory like "user.example" in a future release which you will have to manually rename to avoid it being touched by updates to SUI (ala some CMS etc which include sample config files)

[Serkan Durusoy]

Thank you for the clarification Jack, that's going to be really helpful.