💄 introduce sass #306

[langehm]

Description

• added some css-classes

Reference

Issues #306

[langehm]

Currently only as an example

[langehm]

@FabianWilms I think we need to discuss the file structure here. Formating of the fontface-css files should not be done.
BUT we should include all the manually added css-files into prettifier and eslint!

[FabianWilms]

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?

[FabianWilms]

BUT we should include all the manually added css-files into prettifier and eslint!

Definitely

[langehm]

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?

We currently have manual files in the temp directory :D that is the problem I want to adress

[FabianWilms]

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?

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.

[langehm]

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?

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 ;)

[FabianWilms]

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?

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!

[FabianWilms]

@langehm I reworked the way we import MDE assets and moved our own assets away from the temporary directory with 9baf710 (a breaking change).

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.

[langehm]

scss is working for now. Should we convert all of the stylings in this pr too? @FabianWilms

[FabianWilms]

scss is working for now. Should we convert all of the stylings in this pr too? @FabianWilms

You mean custom-styles.css?

[langehm]

scss is working for now. Should we convert all of the stylings in this pr too? @FabianWilms

You mean custom-styles.css?

yes and no. I meant every use of a custom class or style inside the components if possible to some generated class of the scss.

[FabianWilms]

Sorry I misunderstood your question at first. Yes that would be great to have it consistent!