Your SlideShare is downloading. ×
Gilbane San Francisco 2010<br />T8. Open Source Tools That are Changing the Content Technology Landscape<br />
Presenter<br />Shaun Walker<br />CTO<br />DotNetNuke Corporation<br />- 18 years professional experience in architecting a...
Agenda<br />Effective strategies for evaluating and deploying <br />Open Source <br />Content Management Tools <br />
Open Source CMS<br /><ul><li>Open Source CMS systems have been available for over 10 years
Share many common characteristics but also differ in many fundamental ways
In recent years, many have evolved into Content Management Platforms</li></li></ul><li>Business Proposition<br /><ul><li>M...
Simple acquisition
Large accessible user base
Flexible and customizable</li></ul>               … do they deliver?<br />
Licensing<br /><ul><li>Understanding the most common open source licensing models and terminology
“Libre” vs “Gratis”
GPL
BSD
Dual Licensing
Open Core
Forking</li></li></ul><li>Platform<br /><ul><li>Has your organization standardized on a specific technology platform?
Do you possess in-house resources which are skilled with the technology utilized by the CMS?
What other products does the CMS rely upon and what are the associated costs, licensing models, and business risks to cons...
Upcoming SlideShare
Loading in...5
×

Open Source Web Content Management Strategies

1,608

Published on

DotNetNuke Co-Founder Shaun Walker shares "Effective Strategies for Evaluating and Eeploying Open Source Content Management Tools" at the Gilbane Conference 2010 in San Francisco

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,608
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Transcript of "Open Source Web Content Management Strategies"

  1. 1. Gilbane San Francisco 2010<br />T8. Open Source Tools That are Changing the Content Technology Landscape<br />
  2. 2. Presenter<br />Shaun Walker<br />CTO<br />DotNetNuke Corporation<br />- 18 years professional experience in architecting and implementing enterprise software solutions for private and public sector organizations.<br />- Creator of DotNetNuke, a Web Content Management Platform for ASP.NET which is the largest and most successful Open Source community project native to the Microsoft platform.|<br />- Served as a founding Director for CodePlex Foundation, a non-profit foundation created by Microsoft for enabling the exchange of code and understanding among software companies and open source communities.<br />
  3. 3. Agenda<br />Effective strategies for evaluating and deploying <br />Open Source <br />Content Management Tools <br />
  4. 4. Open Source CMS<br /><ul><li>Open Source CMS systems have been available for over 10 years
  5. 5. Share many common characteristics but also differ in many fundamental ways
  6. 6. In recent years, many have evolved into Content Management Platforms</li></li></ul><li>Business Proposition<br /><ul><li>More economical than proprietary CMS systems
  7. 7. Simple acquisition
  8. 8. Large accessible user base
  9. 9. Flexible and customizable</li></ul> … do they deliver?<br />
  10. 10. Licensing<br /><ul><li>Understanding the most common open source licensing models and terminology
  11. 11. “Libre” vs “Gratis”
  12. 12. GPL
  13. 13. BSD
  14. 14. Dual Licensing
  15. 15. Open Core
  16. 16. Forking</li></li></ul><li>Platform<br /><ul><li>Has your organization standardized on a specific technology platform?
  17. 17. Do you possess in-house resources which are skilled with the technology utilized by the CMS?
  18. 18. What other products does the CMS rely upon and what are the associated costs, licensing models, and business risks to consider?</li></li></ul><li>Development Model<br /><ul><li>Understand the differences in software development models
  19. 19. Pro: Evolves rapidly, embraces new trends, high level of user influence
  20. 20. Con: Not always predictable, roadmap not always clear or even available
  21. 21. Organic vs. Commercial open source
  22. 22. Policy regarding upgrades and the preservation of backward compatibility?</li></li></ul><li>Ease of Use<br /><ul><li>Simple intuitive web-based user interface
  23. 23. Utilizes modern client-side capabilities to create a rich interactive user experience
  24. 24. Most common tasks readily available, less common tasks reserved for power users
  25. 25. New users come up to speed quickly and require minimal training
  26. 26. Has a rich text editor that emulates the features available in modern word processors</li></li></ul><li>Flexible Design <br /><ul><li>Offers flexibility in web design which does not restrict creativity or artistic expression
  27. 27. Supports the most common web design tools
  28. 28. Has a variety of templates available which can be utilized or customized
  29. 29. Has adequate documentation describing the design process
  30. 30. Can identify a number of professional resources who can assist with web design projects</li></li></ul><li>Customizable<br /><ul><li>Provides an Open API and framework which can be utilized to easily build and integrate custom extensions
  31. 31. Allows for deep integration with other systems
  32. 32. Professional software development tools are available and cost effective
  33. 33. Are there many resources available or is the skillset specialized?
  34. 34. Supports software and content localization, multi-tenancy</li></li></ul><li>Extensible<br /><ul><li>Additional functionality can be discovered, acquired, and deployed simply and easily
  35. 35. Terminology: Extensions, Plug-Ins, Modules, Widgets
  36. 36. Free vs. Commercial Licensing
  37. 37. Does the deployment model require IT involvement?
  38. 38. Does a certification program exist?
  39. 39. Is the volume and quality of extensions increasing?
  40. 40. Are they being actively maintained and enhanced by developers?</li></li></ul><li>Scalable<br /><ul><li>Are there reference users which are utilizing the product in high volume environments?
  41. 41. Provides the ability to scale-up or scale-out based on your needs
  42. 42. Is committed to preserving performance baselines as the product evolves</li></li></ul><li>Secure<br /><ul><li>Allows each author or administrator to have their own user account
  43. 43. Allows for security groups or roles to be defined
  44. 44. Has a rich permissions model which provides granular administrative rights to users
  45. 45. Supports multiple authentication systems
  46. 46. Includes full auditing of all changes in the system
  47. 47. Has a public Security Policy</li></li></ul><li>Community<br /><ul><li>Has a large community of users who are vocal and actively involved
  48. 48. Has a central hub where community members can interact with one another
  49. 49. Offers community support services through discussion forums or wikis
  50. 50. Has community representation in your region ( ie. through user groups )</li></li></ul><li>Supported<br /><ul><li>Community support channels have many active participants
  51. 51. Commercial support options are also available
  52. 52. Does the SLA match your business requirements?
  53. 53. Has a variety of commercial partners worldwide</li></li></ul><li>Business Model<br /><ul><li>Vendor-led or Community-led?
  54. 54. Has a strong leadership team which has demonstrated strategic vision and has the confidence of the community
  55. 55. Has an understandable business model which ensures stability, accountability, and longevity</li></li></ul><li>Thank You<br />Ecosystem<br />Commerce<br />800+ third-party DotNetNuke vendors offering 8000+ extensions<br />6 million downloadsgrowing by 100K per month<br />Questions?<br />( Slides will be posted on my blog on www.dotnetnuke.com )<br />500K+ production web sites with 12K new each month<br />500+ active SIs, VARs, and web design firms<br />775K+ members with 250K+ forum posts<br />40+ web hosting partners<br />

×