@a47ae said in Themeing, Stylus vs SCSS: Only thing you currently can’t to is to use the Stylus variables in SCSS/SASS. But I guess one could find a workaround for that. I started working on a (very hacky) workaround… gave up half way through, but maybe someone will find it useful: https://gist.github.com/bikubi/76325574c7c8236d5f14323d52e472ab

Hi, Sorry for late reply, I had to step aside this issue for a few days. What you posted back on Stackoverflow solved my issue. Many thanks for that. stackoverflow

@rstoenescu Thanks Razvan. Using css will work fine for now.

Yes, you’re right. Lists have their own text color. Will fix this in v0.8. You can however CSS overwrite the “color” property (not through stylus variables) of lists on v0.7 until the improvement arrives in v0.8.

@israel965 I ran into the same problem. I finally got the fonts working in “build” distros by providing relative paths from quasar/.quasar So instead of src url(/fonts/OpenSans.ttf) try src url(../src/css/themes/fonts/OpenSans.ttf) obviously, customize the path to your font files, but keep them relative, not absolute I will note this is probably only a good idea for local apps such as electron or mobile apps. Webpack will rename font files, so that cached versions of the fonts cannot be used, which, for a web site, will slow down time to load the initial page significantly.