It just seems to me if you want to do anything with Master Pages in SharePoint–you need Publishing. Even though you can add publishing infrastructure to a Team Site–It seems to be a little of a kluge. Things don’t work optimally.
Consider a simple scenario of changing the home page once you’ve added publishing infrastructure to a Team Site. You need to recreate the home page in the Pages Library. You can’t copy your old home page because isn’t constructed as a publishing page.
Thoughts. Please even blatantly disagree. I’m basing my thoughts on my expirments with 2013 which don’t cover all scenarios that you might find useful for your purposes.
I always use / recommend publishing. I find it easier to control the way it looks and how the sub sites inherit the branding.
The only reason I wouldn’t use publishing is if they don’t have it (Foundations or low level o365)
I’m just trying to see if my analysis squares with others who need to create Custom Master Pages.
My conclusion is:
1) if you need to customize Master Pages its much easier with Publishing Infrastructure: (Site Settings Menus under “Look and Feel” Master Page, Page layouts and site templates, Navigation–plus the options of functional “Term store management”)
2) if you’re going to bother with Publishing Infrastructure–why fool with Team Sites and get less than stellar integration of Publishing Infrastructure.
Just asking have I missed any elephants in my analysis.
thanks,
Stephan
Fabulous. What are the particular issues and how we might help out, then.
