I've created a new skin and set the [solpartmenu] tag to display vertically - no problem, works great.

I've modified the .MainMenu_MenuContainer style to add a border, set a background and align text - no problem, works great.

I've modified the other .MainMenu_* styles - no problem, works great.

The last thing I'm trying to do is add a 1px solid white border around the main menu cells. For instance, my main menu consists of Home, Forums, Blog, Admin and Host. So, I want to put the 1px solid white border around each one of the main menu items and for the life of me I can't figure out where to set that style.

Anyone have some insight before I pull out the few remaining hairs I have left? :)

Mark

That is most likely the reason.

I have done a couple of articles on CSS hierarchy - but in a nutshell, the closer to the file - the louder it speaks and more it is listened to.

• default.css - sits in the _default folder - it's there as a fallback for thing missing in the global portal overview
• If the class is missing from the filename.css, skin.css & portal.css - this will render the class
• portal.css - sits in the portal/0/ or portal/1.. etc folder and it the local management - eg.. of that portal
• If the class is missing from the filename.css and skin.css - this will render the class
• skin.css - sits in the relevant skin folder - and pertains to skins within that folder set
• If there is no filename.css file - this is the normal default file used for skinning purposes
• filename.css - helps you customis a particular skin in within the folder -
• If you have contrasting pages and need to make a specific class stand out in a file - you can add this to enhance the skin

So in summary - In a skin set - I work with common functionality - something that's pertaining to all the skins within a folder.. usually the content panes and stuff... and if I have something that's specific to that skin - I add the filename.skin css - eg... PortalMain.ascx / PortalMain.css  and can further finetune skins within the folder.

There are some other elements to consider though - eg. modules - what classes are they using - in theory you should be able to drop them into the editor from the admin/settings page  which is - in fact.. the portal.css file that resides in the portal/0/ folder

I hope this sets you on the right track

Nina Meiers