Loading ...Hey guys,
a pretty theoretically and interesting article or better: comparison of Sharepoint and Sitecore. I think it’s worth reading, but I’m a friend of creating my own opinion 
Enjoy… cheers chris
This series will cover the following areas:
- Introduction (Part 1)
- Installation and General Architecture (Part 2)
- Configuration (Part 3)
- Customization and Designer Experience (Part 4)
- Integration with Developer Tools (Part 5)
- Feature Deployment (Part 6)
- API und Data Model (Part 7)
- Integration with other systems (Part
- Conclusion (Part 9)
‹ go back // go to overview
Didn’t realize that my article series is that theoretically, but thanks for linking anyway… How is it going with “creating your own opinion”?
I changed the title of the series, maybe you can update your link, too. Would be nice…
Hi Chris. Still “creating your own opinion”?
By the way, I changed the title of the whole series and there is now a part 5 at http://jgnk.spaces.live.com/blog/cns!457F4BDBA1A371A5!309.entry…
I totally agree 100%. Sharepoint is terrible for a developer. If you can deal with the huge limitations out of the box and don’t have to do any coding or customization, OK. Otherwise, you’re better off using another platform. There are so many nuances and bugs within the API, and there are so many different areas and tools that need to be learned and navigated that it makes Sharepoint custom development difficult both to learn and debug. My conclusion:
Sharepoint: simple to use out of the box, impossible to customize.
Although my company is a big advocate of Sharepoint and I’m the main Sharepoint developer for my company, I hate it with a passion and try to steer clear of it and recommend against it as much as possible. It’s much faster for me both in the SHORT and LONG run to create custom applications than dive into that mess of a platform.