-
Notifications
You must be signed in to change notification settings - Fork 141
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
Documentation for Semantic UI React #50
Comments
@base698 will do that soon! |
@xiaohanyu any update on this? thank you for the package. i built all the themes but now do not know what to do with them. i had been following this guide which may help as a basis for your own guide. wondering what exactly i need to copy over from the semantic-ui-forest/dist to the semantic folder in CRA. if you can help me with describing where the theme goes id be happy to write an update for your readme with CRA steps EDIT: see comment below. did not need any of the gulp / |
alright ive messed around with this a bit. i could be way off here but here were the steps i took
example using the flat theme src/
theme/
semantic.flat.css <--- copied from semantic-ui-forest/dist/semantic-ui/v2/
# i believe you only need to copy over the theme asset sub-dir that is needed, not all 4
# it still must be in themes/ because the css file looks for it there
# you could modify the import statements in the theme.css if you dont want to nest the assets
themes/
default/ <--- this is the assets needed by semantic.flat.css
App.js <-- import "./theme/semantic.flat.css"; this seems to work for a few components i tested out (buttons, menus etc). but i see an absolute heap of other files and bits that i am not using which leads me to believe i may be missing some important parts that come up from certain components. do either of you have any suggestions on which of those other files are required? or in what usage they may be required? thanks again |
here is what ive gathered:
|
Links on the site link out the css files, but putting the css as an import fails.
The text was updated successfully, but these errors were encountered: