What CSS structure works well with SharePoint publishing sites?

Question

The past, now irrelevant background: I tried to make some changes to BlueBand and quickly “work and work”, but looking at it further, this is no longer an option due to the tables that the previous developer presented to the layout. I will have to live with it and do some tweaks that I can.

So, looking at future projects of new deposits ...

Are there any recommendations for CSS frameworks that work well with SharePoint publishing sites? (Examples of BluePrint , YUI .) They should not interfere with standard predefined controls, such as the Site Actions menu, rich text editor, and publishing panel.

Real world experience is welcome, please!

Answer 1

What do you want to use the CSS framework for? As far as I can tell, you can use it to create a cross browser reset, but everything else depends only on your layout. If you plan to throw away the standard SharePoint layout, that means you need to start from scratch. The good news is that it is not much different from creating a layout for any other website. There are some things you need ( http://msdn.microsoft.com/en-us/library/aa660698.aspx ) while working with SharePoint, but as for CSS, it is all up to you.

Answer 2

Heather Solomon has a great blog / guide for connecting SharePoint CSS classes - take a look:

http://www.heathersolomon.com/content/sp07cssreference.htm

Greetings

Adam

Answer 3

You will run into a big problem trying to hack the blue bar theme into a smaller table.

You can get some mileage from the free Accessibility for Sharepoint . It comes with breadcrumb pages, CSS, and even control adapters for anyone interested in their site’s HTML site.

However, getting rid of tables created by SharePoint is actually not compatible with "up and running pretty quickly"

Answer 4

You should start with a minimal homepage . This will be the main page associated with publication layouts. Then you can add in all the html / css you want to your main page and layouts so that they look as if you want.

If users viewing the same publication pages also need access to your list formats (new, edit, display), you will have to edit these files and attach them to your main page (either through SP Designer or in a function, it will automatically) . Or, configure the main page of the application in much the same way as the main page of the publication, and deploy them as a function using an HTTP handler that changes the main page for application.master at run time.

Also FYI, there are many problems as soon as you start customizing the list form pages for a site accessible by anonymous users, so do your research first if necessary.

Answer 5

We used 960.gs with some success. Just enable it on the main page and wrap the main content area with - or use container_12 / container_24. Then, in your individual page layouts, you can use all the / push / pull / alpha / omega columns that make 960 so big. It works in 2007 and 2010, in 2007 a little more work is required.

Answer 6

You can use any infrastructure that you need when working with Sharepoint, but the main problem is how much control you have on the web parts. OOB Web Parts use table layout. If you have full control over how web parts use their product markup, then you are one step closer to using a framework with a little headache.

To facilitate a part of the table-based layout used in web parts, you can look at the accessibility tools to properly transform web parts.