SharePoint is a Microsoft-based platform for building web applications. It covers a widerange of capabilities and while it is appropriate for experienced webdevelopers, even non-technical minded users can easily navigate through thesystem and execute functions such as collaborating data, managing documents andfiles, creating websites, managing social networking solutions, and automatingworkflow.
Type | Title | Date | |
---|---|---|---|
Category | Enterprise Content Management | Jul 29, 2025 | Download |
Product | Reviews, tips, and advice from real users | Jul 29, 2025 | Download |
Comparison | SharePoint vs OpenText Documentum Content Management | Jul 29, 2025 | Download |
Comparison | SharePoint vs OpenText Content Management | Jul 29, 2025 | Download |
Comparison | SharePoint vs IBM FileNet | Jul 29, 2025 | Download |
Title | Rating | Mindshare | Recommending | |
---|---|---|---|---|
OpenText Documentum Content Management | 3.8 | 12.1% | 83% | 32 interviewsAdd to research |
OpenText Content Management | 3.9 | 11.1% | 96% | 21 interviewsAdd to research |
Major areas that SharePoint deals with are websites,communities, content, search, insights, and composites. The purpose is to give usersthe ability to create or develop these key business components on their owneven without technical knowledge of, for example, how to build a website or howto integrate coding. Configuring SharePoint into a business's system is meantto cut out all of the complicated steps, and pave the way for easierimplementation all around.
SharePoint was previously known as SharePoint 2007, SharePoint 2010.
Toyota, Aeroports de Paris, ASBBank Ltd., Barking, Havering and Redbridge University Hospitals, CambridgeshireConstabulary, D&M Group, NPL Construction Company, and The Regional Municipality of Niagara.
I would agree with this as you are talking older versions of SharePoint. Even research firms like Gartner and Forrester agree that SharePoint 2013 or 2010 are not built for CMS.
With that said my former team deployed a fully functional CMS on SharePoint in O365. Supporting the requirements you pointed out. We even added in DITA XML support from a publishing perspective.
Was it easy - no. But we did use SharePoint O365 out of the box along with Javascript for all the user experience customizations. And used their API to integrate to applications on premise. What we did learn is from a DevOps perspective, automating configurations between 'environments' was the most complex portion. When I say 'environments' it was automating the configuration between tenants that we used for our dev and UAT environments. Some Microsoft service providers offer solutions but we found them lacking.
Look at SharePoint in the cloud - a much better option than any other version of SharePoint. Of course there are other CMS solutions you should consider, open source or propriety.