@joyknows has posed an interesting SharePoint question via Twitter -
What would you say are the primary strengths and weaknesses of OOTB customisation vs. SPD vs custom code?
This one is definitely going to take more than 140 characters so here goes...
Out of the box (OOTB) customisation allows any end user familiar with SharePoint to create sites, lists and web parts through the user interface to produce something that meets their specific requirements.
- Very quick to create customisations
- Anybody with basic SharePoint knowledge can do it
- Forces users to create solutions in a "SharePoint way" which encourages consistency
- Doesn't provide much flexibility - compromises have to be made with requirements
- If you want to repeat the same customisations again then options for recreating the solution are limited - manual repetition of creation steps or templates
SharePoint Designer (SPD) customisation allows power users to get a bit more creative and make use of some of the more advanced options in SharePoint such as custom workflows and connecting to differnt data sources.
- More options for customisation - will fulfill more of the original requirements
- Make changes to master pages and page layouts - create a completely new look and feel
- Difficult to deploy customisations made using SPD to other sites - eg. A custom workflow created in SPD is applied to a specific list and cannot be resused on another list. The only option is to manually recreate the workflow again for the next list.
- It is possible to do a lot of damage very quickly if put into untrained hands
- Once files are customised by SPD they cannot be changed by custom code
Custom code requires a SharePoint developer to write it but it is the most powerful option that opens up the full SharePoint API, web services and any other code you want to use to customise your solutions.
- Provides the most options for customisation
- Customisations can be packaged up as features that are easily deployed and reused in multiple solutions
- Deployment can be controlled and governed more easily as customisations can only be deployed by people with SharePoint admin permissions
- Requires a SharePoint developer
- Takes longer to achieve the same results
The above lists are a very brief summary of the pros and cons for each option. In reality it would be possible to have lengthy discussions about each but I think these lists provide a fair summary that should help as a primer for the more important discussion - which option should I choose?
As with most decisions like this the short answer is - it depends. In this case it depends largely on the trade off that you are prepared to make between speed of solution develoment and flexibility/meeting the original requrements exactly.
If you need something fast and are prepared to compromise by not meeting the original requirements 100% perfectly then OOTB is the way to go.
If, on the other hand, you need to have a solution that ticks off every requirement perfectly, that can be easily reproduced across lots of sites and you are prepared to wait a bit longer for delivery then custom code is the answer.
SharePoint Designer is a middle ground that combines the best and worst of all the options. In my opinion it should only be used to quickly prototype something that you later turn into a well packaged custom code solution or where you have to customise to meet a requirement but do not have SharePoint development resources available.
In the interests of full disclosure I am from a SharePoint development background and have also spent a significant amount of time working with SharePoint whilst being constrained to only using OOTB customisations. As a result I am not what I would describe as a typical SharePoint dev - ie. Reach for Visual Studio first and ask questions later!
This may sound like a betrayal of my SharePoint developer brothers and sisters but I would argue that custom code should only be used once you are sure that what is being asked for cannot be achieved using OOTB customisation. That may sound obvious but it is easy to take requirements on face value and assume that what the end user is asking for cannot be compromised on which makes it look as though custom code is the only option. In reality if the end user understands that they can have a solution that meets 80% of the requirements delivered in 2 days using OOTB or a solution that meets 100% of the the requirements in 10 days using custom code those requirements that were previously set in stone suddenly become a bit more flexible.
So in summary, and just to be clear so I don't get flamed by all the SharePoint devs, custom code is great. It provides the most number of customisation options that can be deployed to your SharePoint farm in a repeatable and controlled way. However, I would choose OOTB wherever possible in the interests of speed of delivery and productivity even if that means using your powers of persuasion to talk the end user into settling for a solution that doesn't tick off 100% of the original requirements but does meet the core ones, they will thank you in the end!