I'm wondering the same thing that you ask here. Sorry I don't haven an answer for you, but after 18 months hopefully you found an answer to your own question.
Do you have any advice for anyone else who has these same questions? It seems right now that for us to modify the css, we have to just keep modifying stuff, see how it looks, try to track down which particular .css statement is over-riding our desired style, and then trying to continually make our .css more specific to get around the many different cases that are defined by default by Confluence.
It seems that for some reason my "reply" to another thread has turned up as a new thread....
I was originally referring to how you style the pages using css, and that we must know the class and id names used in the base css, and override each of them if we want to get our own consistent look. That takes looking through the .css files, using inspectors etc. to figure out exactly what to override...
Eventually we figured it was just easier to hack the page layout file, and change the "wiki-content" definition in one of the divs to something else, so that all the default css which refers to "wiki-content" is effectively de-activated. We then started fresh with our own css without having to worry about making sure we override every existing css statement.
Hi Community! 2018 was filled with changes for our team, both big and small, and we've taken a lot of time to both celebrate our wins and recognize areas of improvement. One thing that we're a...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs