Welcome back! This blog series is devoted to pointing out some of the key enhancements that SharePoint picked up in the last 10 years.
If you’re still treating SharePoint like the web based file share it was in 2003, it's time for a reappraisal.
In part one we covered some of the base enhancements for capacity and information management. Those foundation elements make sure you have all the “right” documents, and far fewer obsolete ones. Today, we turn our attention to the user experience.
No More Blue Boxes
Literally. SharePoint “branding” used to be a more esoteric science of hand tooled features and CSS files. SharePoint 2010 introduced the seldom-used ability to define custom site themes by using PowerPoint. That was an interesting step (no one ever used it), but now you can make key changes directly from the browser using Composed Looks.
With Composed Looks, a site owner can restyle a site with custom layouts, fonts, colors and background images. You get to the editing screen from the Site Settings menu option. Or just pick “Change the look” from the setting “gear” icon in the top right of the screen.
By default, you’ll see that you start with about a dozen looks. But each look actually contains many font sets, color palettes and layouts. For example, below is the Immerse Look. I’ve used a custom font (Century Gothic), but switched the site’s layout to Oslo to give the floating window look:
Adding that background image is the easiest part. All you have to do is drag and drop a preferred image to the box in the left hand navigation bar. You also have a chance to preview the look before applying it to the site.
One of the constant criticisms I hear about SharePoint is that it still “looks like SharePoint.” To be fair, it was too easy to just let SharePoint proliferate page by page with nothing but a sea of blue boxes — largely because custom branding was not a power user feature.
I like this design — but it’s not for everyone. This site is used principally to aggregate information from multiple sites, so it acts as a “catalog.” We wanted the look and feel to be a little more polished — but that much background imagery might not work on a heavy collaboration site with lots of lists and other busy components. Still, those sites can be restyled with a consistent look and feel.
SharePoint has also added support for more sophisticated page layouts. You can edit master pages and layouts in other applications, like Dreamweaver instead of FrontPage, and nothing substitutes for professional development when sophisticated user experience and interface changes are required.
It’s a strongly recommended adoption technique to not call your farm “SharePoint” — custom host names like “KMANet” or “Cramerville” put the focus on the information, not the platform. Similarly, DON’T stick with the default look and feel. Decide on a look that better reflects your brand, and stick to it.
Coloring the Documents
We’re not talking about actually painting the documents. But in 2003, most documents were “classified” with file names like “Presentation-Mktg-June30-CathyFinal-ProjectAuburn.” That helps if you’re looking at the document itself. But how do you find it to start? How do you know to search for “Auburn” — or worse, “Mktg”? There’s a lot of variability between any two users about how they name documents.
Managed metadata was introduced in 2010, and it provides an answer. You can define key elements of your “taxonomy” in one central place, shared across farms. If you have five departments, you can enter them all as tags and then use that definition anywhere in SharePoint users might be asked to fill in a department:
- 5 Tech Trends We'll See More of in 2014
- The Future of Collaboration Isn't What It Used to Be
- SharePoint Conference Keynote: Releases and Roadmap #SPC14
- Who Leads the Big Data Market? (Probably Not Who You Think)
- The Fall of Collaboration, The Rise of Cooperation
- If You Dress SharePoint Differently, Is it Easier to Use? #SPC14
- Acquia Lift Makes Drupal Sites Smarter, Revenues Bigger