Rikki

Hey Adlago,
I don't work at IPS (despite that cute cartoon avatar I have), so I'm able to tell you that you're doing it wrong. You should never have been editing the default CSS files, and it's unfortunate that the product allowed it all this time.
I assure you, you can do everything you did before. It'll be even better than before, actually, because it won't break on every upgrade.

Hey Adlago,
I don't work at IPS (despite that cute cartoon avatar I have), so I'm able to tell you that you're doing it wrong. You should never have been editing the default CSS files, and it's unfortunate that the product allowed it all this time.
I assure you, you can do everything you did before. It'll be even better than before, actually, because it won't break on every upgrade.

Hey Adlago,
I don't work at IPS (despite that cute cartoon avatar I have), so I'm able to tell you that you're doing it wrong. You should never have been editing the default CSS files, and it's unfortunate that the product allowed it all this time.
I assure you, you can do everything you did before. It'll be even better than before, actually, because it won't break on every upgrade.

Hey Adlago,
I don't work at IPS (despite that cute cartoon avatar I have), so I'm able to tell you that you're doing it wrong. You should never have been editing the default CSS files, and it's unfortunate that the product allowed it all this time.
I assure you, you can do everything you did before. It'll be even better than before, actually, because it won't break on every upgrade.

Also, you can still view the full (concatenated) CSS files in web inspector. Just click the filename:

Then the format button:

Maybe y'all develop differently to me, but personally I wouldn't browse through a random CSS file to find classnames - there's no context (beyond the classname anyway; you don't get any of the cascade, inherited properties etc. that might affect it).
It makes much more sense to use the web inspector to see what is actually being applied to the element you want to change.
It may be a difficult transition at first but i would consider this an opportunity to improve your own development process.

Also, you can still view the full (concatenated) CSS files in web inspector. Just click the filename:

Then the format button:

Maybe y'all develop differently to me, but personally I wouldn't browse through a random CSS file to find classnames - there's no context (beyond the classname anyway; you don't get any of the cascade, inherited properties etc. that might affect it).
It makes much more sense to use the web inspector to see what is actually being applied to the element you want to change.
It may be a difficult transition at first but i would consider this an opportunity to improve your own development process.

Also, you can still view the full (concatenated) CSS files in web inspector. Just click the filename:

Then the format button:

Also, you can still view the full (concatenated) CSS files in web inspector. Just click the filename:

Then the format button:

Maybe y'all develop differently to me, but personally I wouldn't browse through a random CSS file to find classnames - there's no context (beyond the classname anyway; you don't get any of the cascade, inherited properties etc. that might affect it).
It makes much more sense to use the web inspector to see what is actually being applied to the element you want to change.
It may be a difficult transition at first but i would consider this an opportunity to improve your own development process.

Maybe y'all develop differently to me, but personally I wouldn't browse through a random CSS file to find classnames - there's no context (beyond the classname anyway; you don't get any of the cascade, inherited properties etc. that might affect it).
It makes much more sense to use the web inspector to see what is actually being applied to the element you want to change.
It may be a difficult transition at first but i would consider this an opportunity to improve your own development process.

Maybe y'all develop differently to me, but personally I wouldn't browse through a random CSS file to find classnames - there's no context (beyond the classname anyway; you don't get any of the cascade, inherited properties etc. that might affect it).
It makes much more sense to use the web inspector to see what is actually being applied to the element you want to change.
It may be a difficult transition at first but i would consider this an opportunity to improve your own development process.

Also, you can still view the full (concatenated) CSS files in web inspector. Just click the filename:

Then the format button:

Also, you can still view the full (concatenated) CSS files in web inspector. Just click the filename:

Then the format button:

Maybe y'all develop differently to me, but personally I wouldn't browse through a random CSS file to find classnames - there's no context (beyond the classname anyway; you don't get any of the cascade, inherited properties etc. that might affect it).
It makes much more sense to use the web inspector to see what is actually being applied to the element you want to change.
It may be a difficult transition at first but i would consider this an opportunity to improve your own development process.

Maybe y'all develop differently to me, but personally I wouldn't browse through a random CSS file to find classnames - there's no context (beyond the classname anyway; you don't get any of the cascade, inherited properties etc. that might affect it).
It makes much more sense to use the web inspector to see what is actually being applied to the element you want to change.
It may be a difficult transition at first but i would consider this an opportunity to improve your own development process.

Maybe y'all develop differently to me, but personally I wouldn't browse through a random CSS file to find classnames - there's no context (beyond the classname anyway; you don't get any of the cascade, inherited properties etc. that might affect it).
It makes much more sense to use the web inspector to see what is actually being applied to the element you want to change.
It may be a difficult transition at first but i would consider this an opportunity to improve your own development process.

Maybe y'all develop differently to me, but personally I wouldn't browse through a random CSS file to find classnames - there's no context (beyond the classname anyway; you don't get any of the cascade, inherited properties etc. that might affect it).
It makes much more sense to use the web inspector to see what is actually being applied to the element you want to change.
It may be a difficult transition at first but i would consider this an opportunity to improve your own development process.

Set it in custom.css and then you'll never have to worry about conflicts or updates again.
That's literally how CSS works (the C stands for Cascading).

Set it in custom.css and then you'll never have to worry about conflicts or updates again.
That's literally how CSS works (the C stands for Cascading).

Set it in custom.css and then you'll never have to worry about conflicts or updates again.
That's literally how CSS works (the C stands for Cascading).

Set it in custom.css and then you'll never have to worry about conflicts or updates again.
That's literally how CSS works (the C stands for Cascading).

Set it in custom.css and then you'll never have to worry about conflicts or updates again.
That's literally how CSS works (the C stands for Cascading).

Has anyone really been far even as decided to use even go want to do look more like?