Mythe II: SharePoint as WCM
SharePoint is not a Web Content Management system (WCM) for building websites. It’s possible, but not recommended. Microsoft had big plans to make SharePoint more suitable for WCM, but this ambition changed after SharePoint 2013. Who remembers the Ferrari website running on SharePoint 2007? However, the world has changed and so did Microsoft. I still meet clients who are convinced of the Web CMS possibilities. My advice: use WordPress, Joombla or, if there are many custom wishes, DotNetNuke or SiteCore (if a significant budget is available). Just don’t make life too difficult for yourself and your customer.
Mythe III: SharePoint as Application Server
For a while, SharePoint was pushed as an application server for complex custom software solutions. Sometimes it was valuable, but most of the time it turned out to be far too complicated. Clients were dissatisfied with the final product and partners had to pay to solve unforeseen problems. The result: SharePoint got a bad reputation. SharePoint is the perfect base to build applications, as long as there are no modifications on a local server. With the arrival of SharePoint Online you can’t go wrong with custom solutions. It has become less appealing to build applications you actually shouldn’t want to have. SharePoint Add-Ins and the new Client Side Webparts run their codes completely outside SharePoint. This makes these solutions much easier to manage, integrate and migrate. Thanks to PowerApps, Flow and the Common Data Model, you can build powerful and versatile business solutions, without a custom code. And if it’s really necessary to add a unique functionality, you can integrate properly with Azure and Office 365 APIs.