-
Notifications
You must be signed in to change notification settings - Fork 0
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
💄 introduce sass #306 #307
base: beta
Are you sure you want to change the base?
Conversation
Currently only as an example |
@FabianWilms I think we need to discuss the file structure here. Formating of the fontface-css files should not be done. |
I think this goes for all files coming from MDE directly - so everything in the temp-directory? |
Definitely |
We currently have manual files in the temp directory :D that is the problem I want to adress |
Which idiot thought this was a good idea? Yeah we should definitely move them one folder up. This would sadly require a breaking change release. |
It is what it is ... no seperate folder just one up? I don't know who is meant by this but I certainly don't think he/she is an idiot ;) |
I'm open to suggestions and don't really have a preferred opinion. A new folder could be more organized but might never contain more files. You decide! |
…irectory This change requires users of the lib to fix their imports. Please refer to the 'Getting Started' section for the new way to import the required assets.
@langehm I reworked the way we import MDE assets and moved our own assets away from the From here on you can continue to implement the SASS-enhancement. If you're really fancy you can combine all our "custom" css files into one in our build, so we're no longer required to import our two custom css-files seperately. |
Description
Reference
Issues #306