Hi
I have been been using the customised skin option with the atomik theme, and generally it is quick and easy. Mostly I have been able to achieve what I want.
However there area couple of issues:
Perhaps I am stupid but there seems to be no description of what the “primary”, “secondary”, “Light”, “accent” and “dark accent” colours affect in the actual template.
I have looked at the " Customize Colors" in the developers documentation and whilst it describes how to change the above colours, it does define what each colour changes in the template.
The customise skin option does not allow the changing of the nav colours, normal, hover and selected etc. Indeed the colours in the top nav seem to different to the colours in the auto nav block I am using in the side bar.
The customise skin option creates a css file in application/files/presets this is one of those css file with everything in one line which I find “mind blowing”.
My question is it possible optmise nav colours in the css file mentioned above ? Assuming that it is possible to find where these colours are defined in this css file ?
Is it possible that css file in the application/files/presets directory could be created in a “structured” form ? so beginners like me could understand it ?
Sorry, I forgot. The colour issue also affects the Breadcrumbs, should this be changed in the files in the standard atomik set up ? are the breadcrumbs, auto nav colours etc inherited from the standard atomik theme into my custom skin ??
Edited Note:
I have discovered by trial and error that the primary colour affects the nav text. It seems however that the top nav acts differently than the auto nav in the side bar. The selected page nav text in the side bar has a blue colour, whilst the rest of the text is the dark green that I want .
The dark green I set as primary also turns up in the link text in the rich text editor,
So I have solved my immediate problems, but it would still be useful to know where “primary”, “secondary”, “Light”, “accent” and “dark accent” colours appear.
So you can get a sense of where these things are used by going into your terminal and using the grep command in the atomik theme directory like so (make sure to escape the dollar sign with backslash):
I checked my custom skin css file in application/files/presets and the autonav active colour is set to #4a90e2 which is the blue shown in the above screen shot although the primary colour set in my custom skin is #607124 which is the dark green shown above
What a bummer (if I am allowed to use that word) … The above screen shot was taken just after I done the modifications in backend. After I logged out I checked the site it another browser and the active colour was back to blue again. When I reopened the site in the back end then the dreaded blue was back.
Is the custom skin css file in application/files/presets compiled ?? There must be something somewhere that overridden my changes.
I would certainly be happy to mark as solved - your help was greatly appreciated - but cannot see how to mark it as solved. I am logged into the forum but cannot see any button or tab in which I can mark as solved.
Generally I have found Concrete cms as an excellent system and I am well on the way to create a new website. If I have one criticism it is the documentation. I know that documentation is very time consuming and probably tedious for the knowledgeable person, but for a new comer as I, it is very important.
It could be worth while to take the subject of this thread to illustrate my point.
The Custom CSS, Add Custom CSS tab at the bottom of the customise skin tab would benefit from a short note such as: :
“Add or modify your css code here. Your modified code will be included and compiled into your custom skin specific css file located in application/files/presets directory. Your skin specific css file will not be overridden in any future upgrades.”
Yet another issue here is when you open the tab and insert the custom css code into the window there is no button like “save” or “compile” you have to exit the window and then the compiling as executed and it is necessary to save using the tab in the bottom right hand corner. Obvious, I am sure, to experienced, but contra intuitive to the inexperienced like me.
the lack of the “Save” button is an oversight in my opinion and saving your own CSS is confusing, probably not only for you and me - there are several other places like this.
As the author of the post, you should be able to mark the question as solved here.
