In SharePoint 2010, if you activate Publishing, you still get the Pages library and the Images library (you almost forgot it created the Images library - I almost did), however, in general, when creating pages for a SharePoint 2010 site, there are two new libraries that are generated - Site Pages and Site Assets:
If you create a Team Site, these come with it, otherwise they will be created when you select Edit Page or New Page. Site Pages will store all of the site pages and Site Assets is used to store any types of media or files (e.g. images, audio, video, etc.) that are used in the pages. So now we don't need to activate Publishing just for the sake of having consistent storage of our pages and images.
Before you activate Publishing, it does not appear as a valid site creation option, however, there are still nice Collaboration type sites to create:
Notice the icons for these types of sites and the overall presentation. Now, a Publishing Site will appear as an option once you activate the Publishing features - but guess what that looks like:
It is stuck under "Blank & Custom" and doesn't even have a pretty icon to go with it. Hmmm...I'm picking up 1000 words right now.
To the defense of our boring Publishing Site icon, it also appears under the Content & Data category:
Notice it has a friend in there with it now - Publishing Site with Workflow. The workflow one has a nice icon.
This also tells me something.
Since we don't need publishing sites anymore for the wrong reasons, why do we need a publishing site? In SharePoint 2010, I see Publishing Sites being solely used for what they were designed for - the publishing, versioning, and approval of content. This usually involves the need for some sort of approval workflow. Hence, I think we'll see more Publishing Sites with Workflows and less Publishing Sites for the sake of having a Pages libary- all thanks to the new site structure in SharePoint 2010.
1 comments:
Interesting post as I find this topic quite confusing. If I may I would like to ask the following.
I am helping a client create a branded portal based on a site template I have built for them. I have the (sc level) SharePoint Server Publishing Infrastructure enabled but not (site level) SharePoint Server Publishing. The latter is really because we’re in the dev phase so want to create templates etc. This has been fine but now we starting to build killer content.
I am now at a crossroads as the above scenario is leading to some inconsistencies. Namely,( wiki ) created in the Site Pages folder don’t require approval where as a document library set up by the client to store web part pages does require content approval; though I could turn this off. I forgot to publish a page I had recently changed in this document library and my testers were bemused to see the changes they had requested not displayed!!!!!!
I am thinking now it is time make a decision on enabling the SharePoint Server publishing. If I enable: get a consistent location for all pages and a consistent approach to content Checkin/ Approve/ Reject Publish and content, web parts etc. I guess this would move stuff out Site Pages into Pages - not sure whether we still need the document library I mentioned. After all this, I and I can encourage the client to start using custom layouts etc.
Please let me know your thoughts…
Post a Comment