Scoped Bootstrap for SharePoint

By -
I've got a project for a client that involves refactoring a lot of bad choices related to SharePoint branding in Classic mode sites.   (While I'm enthusiastic about the Modern Sites and new techniques using SPFx extensions, most of our customers are slow on the uptake).

I've had to do this a few times and this blog explains it perfectly, but due to some formatting issues over there and a desire for just the steps as I need to update/repeat this, I've summarized here:


  1. Open up a node capable command prompt (I use cmd)
  2. Create a directory for your solution (e.g. C:\Repos\ScopedBootstrap)
  3. Run npm install bootstrap@3.3.7 (or whatever version you need to work with)
  4. Go into the node_modules\bootstrap\less directory 
  5. Open bootstrap.less in VS Code.
  6. Place  .YourUniqueClassName{  before all the @import statements and close the curly brace at the end of the file.
  7. Go back to the ..\bootstrap directory (in node_modules)
  8. Run npm install to install the dependencies
  9. Run grunt dist
  10. Go to the node_modules\bootstrap\dist\css directory in the project and grab the css file you need.   If you open it you should see YourUniqueClassName appended to each seletor.   
  11. Once you reference this file it allows you to enable bootstrap at a certain level of the DOM simply by including .YourUniqueClassName in any elements that need it.   You can do it at a parent node level to affect everything else in the tree below.


Comments

Post a Comment

Popular posts from this blog

ERROR: Failed to create feature receiver...

By -
I was working on a STSDev project which deployed a feature with a feature receiver. I had the feature working without the FeatureReceiver but as soon as I added the FeatureReceiver related attributes to my <Feature> element I got the following error: Failed to create feature receiver object from assembly "Org.Project.Solution, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c632353d405b3209", type "Org.Project.Solution.MyFeature.FeatureReceiver" for feature 6a9b2358-ea4e-486d-a4e4-4f813c52ce88: System.ArgumentNullException: Value cannot be null. Parameter name: type at System.Activator.CreateInstance(Type type, Boolean nonPublic) at System.Activator.CreateInstance(Type type) at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject() After much digging around I discovered that STSDEV's Solution config file refers to a namespace as well as the dll. My FeatureReceiver's namespace was not prefixed with the right namespace So just
Read more

Programmatically Update Page Layouts

By -
I updated my page layouts that I deployed as a feature, but found that I could not overwrite the Layout File. The solution was to add a new page layout and then you would have to associate the new layout with every page on your site that used it. Obviously with a site of any size you'd have a lot of manual work to get this done, so doing it programmatically makes for a much better (and thorough) approach. After you've got your new page layouts, you could do something like this (in your event receiver class): public override void FeatureActivated(SPFeatureReceiverProperties properties) { //replace current page layouts with new page layouts on all pages SPWeb web = SPContext.Current.Web; SwapPageLayout(web, "FullWidthContentWithTitleV1.aspx", "FullWidthContentWithTitleV2.aspx"); } private void SwapPageLayout(SPWeb web, string oldPageLayoutName, string newPageLayoutName) { PublishingWeb pubWeb = PublishingWeb.GetPu
Read more