Concrete5 Root "css" and "js" Folders

Permalink
Hey all,

Here's a total noob question for you: what is the purpose of the "css" and "js" folders found in the root of a C5 install? I get that the "blocks", "page_types" and "single_pages" folders are used to add new elements of those kinds... or to overwrite default elements from the same folders inside the "concrete" subfolder.

But why would I want/need to use these "css" and "js" folders? Isn't all of the css and js code needed for a theme installed inside the theme folder?

Thanks!

arrestingdevelopment
 
kappi replied on at Permalink Reply
Just a quick guess but I would have thought that they relate to the cms structure itself.

That would be my first train of thought anyway
arrestingdevelopment replied on at Permalink Reply
arrestingdevelopment
I thought so, too. But they're empty... and I would guess that any code relevant to (or necessary for) the CMS install itself would be under the "concrete" subfolder, since C5 is good at keeping their code separate from ours (or, rather, they make it easy for US to keep OUR code separate from THEIRS, LOL!).

- John
Tony replied on at Permalink Reply
Tony
those are for either overriding core functionality or for extending the core with your own website customizations. The reason that it's duplicated is to make upgrades easier, cause if you modified the core folders then you'd loose changes after updating.
arrestingdevelopment replied on at Permalink Reply
arrestingdevelopment
Ah-HAH! So that would be like if I wanted to re-style the editing toolbar and nifty-neato stuff like that?!

Kewl! Knowledge is power! ;D

Thanks!
Tony replied on at Permalink Reply
Tony
haven't really heard of people doing that before, but sure. more commonly overriding pages like register, login, page not found (single pages, controllers), overriding core and package blocks or adding block templates, creating custom themes, customizing emails, etc
arrestingdevelopment replied on at Permalink Reply
arrestingdevelopment
Tony,

Wait... so I can change the appearance/functionality of the register, login, page not found (single pages, controllers), etc by adding CSS or JS code to the "css" and "js" folders in the ROOT of a C5 install?

But if I wanted to create a custom theme, doesn't all of it's CSS & JS code get installed into its own subfolder under the "themes" directory? How would I use code in the root "css" or "js" directory to apply as a custom theme?

And wouldn't blocks go into the "blocks" folder? Or do I put CSS that styles those blocks into the root "css" folder?

Sorry if I'm being thick... I'm just trying to understand the purpose of all of the folders in the root.

Thanks,

- John
Tony replied on at Permalink Reply
Tony
not to be rude, but I don't really feel like going too in depth on this stuff since it's been discussed pretty thoroughly elsewhere, in the forums and in the documentation section. This book also goes into detail about the folder structure and customizing things like single pages:
http://www.amazon.com/concrete5-Beginners-Guide-Remo-Laubacher/dp/1...
kappi replied on at Permalink Reply
That's brilliant, I've been wondering for a while about 404 pages and access etc and will now put it on my list of 'to do'.

The more I play with C5 the better it gets
arrestingdevelopment replied on at Permalink Reply
arrestingdevelopment
No offense taken, Tony. But I'd love to be pointed to clear documentation of the use/purpose of the directory structure. I haven't found it yet in my searching (which I'm sure is a result of not knowing what to look for, LOL! ).

Anyone have any other good links/resources? I'm all ears!

Thanks.

- John
Tony replied on at Permalink Best Answer Reply
Tony
http://www.concrete5.org/documentation/developers/system/directory-structure
arrestingdevelopment replied on at Permalink Reply
arrestingdevelopment
DOH! How'd I miss THAT?!? (other than potentially being blind, deaf and dumb?!?!)

Thanks for the link, Tony! I'm also looking at the sample of the book you referenced... looks like I need to get me a copy, too!

Thanks again!
- John