If you get adventuresome in your SharePoint 2013 master page, you can add, edit and delete options from the Site Actions menu. It is a pretty handy thing to do, For example, do you miss the direct access to Site Permissions that SharePoint 2010 provided? It is an easy thing to add with a master page modification. But there are four Site Action menu items that stubbornly stick around and are seemingly unchangeable. However with a little CSS we can do what we please. Continue reading Changing or removing the seemingly unchangeable options in SharePoint 2013 Site Actions
One of the hidden gems in SharePoint is the EditModePanel. This control can be used in a multitude of ways, including altering your page layout to better suit the page in edit mode when you have a restricted width or more complex design. Continue reading Effective Use of the EditModePanel in SharePoint Page Layouts with Complex Designs
Vesa Juvonen of Microsoft has created a GitHub project that demonstrates how to make the out of the box seattle.master user experience responsive without a need to modify the mater page as such, but rather to take advantage of the AlternateCssUrl property in Web level.
Check out the GitHub project: OfficeDev/PnP
This project uses the CSS provided in my Making seattle.master Responsive blog post.
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
“Sonny, true love is the greatest thing in the world. Except for a nice M.L.T., a mutton, lettuce and tomato sandwich, where the mutton is nice and lean and the tomato is ripe. They’re so perky. I love that.”
You know what else would be the greatest thing in the world? A responsive version of SharePoint 2013’s Seattle master page. While an ETA continues to be dodged for this juicy addition for SharePoint on-premises and SharePoint Online, we can play Miracle Max and do it ourselves. Yes really. At the end of the day, it is just CSS. That we can do. Continue reading Making seattle.master Responsive
For years I have told students who were creating new page layouts for their SharePoint publishing or Enterprise Wiki (in the case of SP2013) sites that they can optionally delete the default page layouts that come with the site. I am here to officially rescind that advice! Continue reading Don’t Delete OOTB SharePoint Page Layouts
The waffle, the grid, the thingie in the left corner of your Suite Bar… the SharePoint Online (SPO) app launcher has many descriptions and is one of the latest changes made to SPO. It gives the user fast access to apps and even allows you to customize what is listed and the order. It is a pretty nifty thing. But what if you want to brand it? Or take away an option because you don’t want all of your users accessing it? Continue reading Customizing the SharePoint Online App Launcher
There has been quite the chatter happening on the ole’ interweb lately surrounding the topic of branding and site customization for SharePoint Online (SPO). The overall message people keep hearing is “don’t use custom master pages for SharePoint Online.” Since branding is my schtick, this makes me die a little on the inside each time I hear it. But please hear me when I say this… blanket statements are rarely applicable to everyone involved and should by no means be considered as a rule for life. Yes, you can use custom master pages with SharePoint Online. Yes, it will involve work. But there is no such thing as custom branding without work. The issue is lack of control, and that is a scary thing to face. So let’s recap what has been happening and then I will chime in with my two cents since that is what blog posts are for anyways. Continue reading To brand or not to brand, that is the SharePoint Online Question
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