So we now have the HTML and CSS set for how we want the SharePoint site to look, the next step is to get it as close as is possible to the template in SharePoint, but first of all let’s make sure we have the necessary features in SharePoint enabled to support the Publishing feature.
Browse to the Site collection hosting the site, and ensure that you have the following feature enabled:
SharePoint Server Publishing Infrastructure
In part one of this series of posts we basically got everything ready so that we can start improving the EmployeeTraining Template to ensure that it works and looks good in our production environment. In this next post we are going to achieve the following:
Tweak the CSS template and lay everything out so that it’s ready to bring over into our new Master page.
At Rackspace we have a gym in our office buildings and we also run free classes that Rackers can sign up to. The original gym site is based on one of the Fab 40 templates (Employee training and scheduling) which ‘kind of’ migrated fine over to our new SharePoint 2010 farm. However, it is very flaky and even the smallest change to the Workflows broke it. The gym manager has asked me to create a new site and make it look nicer than the SharePoint defaults.
One of my more recent headaches has been to set up an ADFS environment on some Lab Servers to try to replicate an issue that one of our customers had on their environment. My knowledge of ADFS is average at best before this venture and trying to find good articles out there that helped was not as easy as I thought it would be. I could find several that accommodated a “Test environment” install, but what if you need to do this in production?