Home » sharepoint » Applying Developer Fundamentals to Customizing SharePoint 2013

Applying Developer Fundamentals to Customizing SharePoint 2013

The same fundamental principles of software customization apply to developing new components for SharePoint Server 2013. In other words, it is important to conceptualize the task at hand, as well as the ramifications of the plan on the future operation of the platform. If the project is successfully conceptualized, then care will be taken to use the right methods to ensure continued proper operation of the rest of the platform.

Yaroslav Pentsarskyy presents this important requirement in a video tutorial available for viewing to all subscribers to SharePoint-Videos.com: Most Common Customization Requests. The video also presents the three most popular types of customization requested for SharePoint:

  • Look and UI Interaction
  • Content
  • and Process

These three types are very broad. So Yaroslav defines them further with examples of specific customizations requested by users. It’s worth noting he includes “Disable Out of the Box Functions”, “Site and List Templates”, and “Pulling External Content” within the “Content” customization type. “Workflows”, and even “Deployment” are included within the “Process” type of customization request.

For large communities of SharePoint users, it makes sense to include “Deployment” as a popular customization request. Managing key features of branding — include organizational logos, images, and how objects are organized on pages — to ensure a consistent implementation across a large farm, is a reasonable requirement. Organizations, as well as their key graphical emblems, differ widely, so a custom deployment solution incorporating organizational-specific features is certainly an example of a “typical” customization.

The important point in this video, which is made very early into the nearly 9 minutes of presentation, is to use tools specifically designed to deliver successful customizations for SharePoint to produce the desired result. These tools should incorporate the controls required to ensure no disruption to the overall performance of SharePoint Server 2013. Opting to proceed in any other manner should be deemed too risky an alternative to pursue.

Ira Michael Blonder

© Rehmani Consulting, Inc. & Ira Michael Blonder, 2013 All Rights Reserved