CSS Asset Hierachry

Squiz Matrix Support
1

So I am creating customisations of a design and am finding that CSS Assets won't work with these customisations unless they are children of the Customised Design Asset. This is problematic because as a result it seems that I will need to clone the CSS Assets across all my customisations.


Am I doing something wrong? The hierachy I am having to use is the following…


    design
      |
      +- design-customisation
      |    |
      |    +- css-asset
      |
      +- design-customisation
           |
           +- css-asset


But I want to do this and share the same CSS Asset with both customisations...

    design
      |
      +- design-customisation
      |
      +- design-customisation
      |
      +- css-asset


Tell me I'm dreaming.
2

With the new Design Folder in Matrix v3.4.0, you will be able to implement the second option (by placing the CSS asset directly beneath the Design Folder). Essentially, you can do it now, by putting the CSS asset within your site instead of underneath the customisation. As long as the CSS file gets a URL, it should be fine.

3

Thanks Avi, the design folder sounds promising. Until then I might place them under each site as you suggest.


I have another question, I am attempting to create a menu here is the code so far…
     
    •    
         
      •  
       


So this is a collapsing menu utilising the "settings.*.*" feature.

Everything is working as documented so far, the only problem is that I really need another setting state. I need to use another class to show the case where there are child-pages below a page, but the page in question does not fall within the current hierarchy.

Kind of like in OSX when you have a list view in the finder. If your click on a triangle next to a directory it opens and the triangle turns downwards and the sub-items are indented, you know if another one inside there is a directory because it will have another "closed" triangle. You could consider this state to be a "normal-haschildren" one. Some might see a need for a "current-haschildren" and "hierarchy-haschildren" option as well.

Is there a way to fudge this, or should I start looking into the code?
4

There's no way to do that right now. You could start looking into the code, or submit it as a feature request in the bug tracker. However, it will require additional database queries, as the system needs to check every displayed asset for possible children – something that could be quite resource intensive for every page load.