I have updated the “Just the Essentials” SharePoint Master Pages for SharePoint 2013 post to include a cleaned up and commented version of seattle.html to use with Design Manager.
Continuing the tradition started with SharePoint 2007 and SharePoint 2010, I have put together and posted several different master page files (and one HTML file) for use with SharePoint 2013. Every file is heavily commented and provides a lot of information about what code is necessary for various SharePoint functionality and content. Due to the continued use of the enhanced user interface elements added to SharePoint 2010 and carried over to SharePoint 2013 along with new additions such as the Suite Bar, there are specific HTML elements, IDs, controls and classes that need to remain in place in the master page. You can’t take a total slash and burn approach to developing a custom SharePoint 2013 master page. So in short, read the comments!
Posting 2013 master pages in 2015? Yeah… I know. This has been on my to do list for a long time and between teaching and kiddos, I just didn’t get to it. But I will make up for it by posting SharePoint vNext master pages as soon as humanly possible or within a month of final product release, whichever comes first.
Continue reading “Just the Essentials” SharePoint Master Pages for SharePoint 2013
“Go ahead, be gone with it. And get your sexy on.”
Welcome session attendees and anyone else who happens to wander on this page. This blog entry is a post session review of resources mentioned and code used in our Bring Sexy Back to SharePoint and Gaining Total Control of Your Sites with Data View Web Parts sessions from April 2014 SPTechCon in San Francisco. Continue reading SPTechCon San Francisco April 2014 Session Review
Randy Drisgill posted this little gem awhile back for SharePoint 2013, “Design Manager Bug – SharePoint 2013 RTM“, which includes info about a bug that he discovered when using a Design Manager created master page. The “Apps you can add” portion of the addanapp.aspx screen can come up missing. The screen just ends after the Noteworthy section. I have also discovered that this isn’t limited to just master pages generated by Design Manager, it can happen with any custom master page that you created manually or imported, etc. Continue reading Missing “Apps you can add” with custom master page in SharePoint 2013
The final post of a three part series, Heather Solomon and Dustin Miller are exploring the ever-popular “Mega Menu”, and how to create a powerful, styled and functional mega menu for use on your SharePoint sites. The first post explored the HTML markup and CSS needed for navigation, organized into an unordered list. The follow-up post walked through the use of navigation taxonomy and the XSL for the menu. This final piece will first show how to implement the custom view in your master page, and then enhance it further with some shiny new CSS. Continue reading Mega Menu for SharePoint – Part 3 of 3
Understanding SharePoint:CSSLink and how to add your custom CSS in SharePoint 2010
CSS is a wonderful tool for branding SharePoint; unfortunately SharePoint 2010 has done a decent job of making things pretty hairy and confusing with working with CSS in a SharePoint site. Something we get asked all the time in our classes is “where do I link to my custom CSS file?” Great question and the answer isn’t just “from your master page”. Continue reading SharePoint CSSLink
Yes, the SharePoint navigation really can work for your needs
A commonly misunderstood component of SharePoint is the navigation. We are frequently asked in class about how to make changes to the navigation and when we cover it, people are really surprised and honestly, it is pretty anti-climatic! Here are a few things everyone should know about manipulating SharePoint navigation. Continue reading Working with the SharePoint Navigation
SharePoint master pages, who needs them anyways?
A common misconception about SharePoint master pages is that you need several of them. In our SharePoint UI/UX class, Dustin and I meet people who have created several master pages for their SharePoint sites(s) due to branding and site layout needs. Based on design differences, a master page is created for the home page, another master page for the sub pages, and perhaps even another master page for sub site(s) that need different branding and/or layout. There are very few reasons to have more than one master page, and differing home page vs. sub page vs. sub site designs isn’t one of them. Continue reading SharePoint master pages, who needs them anyways?
Ahh, the list is ever growing thanks to contributions posted by others. I have updated the list of bugs when switching to IE=9 or IE=edge in a SharePoint master page. Go to the bug list.
Branding SharePoint can be a great experience or can be a swirling vortex straight into coding hell. It can also fall anywhere on that scale. Help avoid a swirlie by checking out these top mistakes in SharePoint branding. Continue reading Top 5 Mistakes When Approaching SharePoint Branding