`content.scss` is now over-riding my `custom.css` ...
# questions
a
content.scss
is now over-riding my
custom.css
and I can't seem to fix it even with
!important
, making me unable to change my font-size stuff. Is this due to "file" calling order and has changed? It was working properly <24 hours ago before
v0.97
.
Still not sure how
_app.js
works, but (after prettier) my
custom.css
is being called on line 20,914, then
content.scss
is being called on line 27,396 which completely eliminates any of my custom stuff if it appears in there.
s
Sorry about that, I'll look into this to see why it's overriding the custom theme.
@AshSimmonds Are there any specific elements that are getting overridden? The sample theme seems to work for me,
content.scss
is not overriding anything I have set.
a
Per screenshot above:
font-size
for one.
s
Sorry about that. The breakage is a bit expected since we haven't stabilized the properties yet, but I was able to change the font size by using a more specific selector. Can you try:
Copy code
css
main.main-content {
  font-size: 1.25rem;
}
a
Thanks, but I don't think having a specific selector that the end user needs to discover is the goal here though. The user's
custom.css
should be the first source of truth, with all others a fallback option.
s
I definitely agree that the styling needs to be simplified in a way where it can serve as a source of truth. Right now the custom styling is a early look that's not complete, and we appreciate you testing it out and finding which parts work and which parts don't! We'll keep this in mind as we work to improve it.
a
Cool bananas. I think the low hanging fruit is to make
custom.css
the final say for the user. Took me an hour of spelunking through obfuscated code to figure out why my stuff didn't work - most folk will hit that wall much earlier and deflect to something easier.
3 Views