Cherry Bekaert LLP
@KevinGuyer




Cherry Bekaert – 900/1000 employees
2 SharePoint developers/administrators

Scott Jones and Kevin.
 Implementation help from TCSC
2010 implementation, fleshing out a 2013 farm now
 Implementation details:





Limited MySite usage
Use managed metadata and central template hub extensively
Vigilant about not installing 3 rd party web parts and plugins to the servers
Content is user managed, structure is typically managed by the 2 of us with Marketing’s guidance.
All sites are ‘publishing sites’

 Goal: Provide targeted news and content for our users. Our org follows a hierarchy and the content and delivery options should reflect that.
 Solution: A combination of managed metadata structuring, content types,
CQWPs, modified XSL stylesheets and audiencing.

Offices have a page with news, that rolls up to their ‘market’

Mapping Term Sets to Site Columns

Default a list’s mapping so user does not have to fool with it

Filter CQWPs based on metadata, audience those parts

 Rotator – Marketing news banners

Foobar – Firm notifications
 Publishing Site News Rotator –
Dynamic from Pages
 Calendar Viewer – One click add to
Outlook

The custom list lets the user provide show/hide dates, applicable areas for filtering and flag as ‘published’

Firm-wide ‘Foobar’ Alerts

Controlled via a custom list, accessed via a small client-side piece of JavaScript
With jQuery. Alerts can be made active/inactive and edited at any time.

Publishing Site News Rotators

They only edit here
Standard implementation, ready for non-developers to use

Calendar Event Viewer

Change a few settings in the text file, embed in page, done.

Code: http://kevinguyer.squarespace.com
or just Google:
‘cheapskate's guide to SharePoint 2010’
@kevinguyer
Questions