Drupal Distributions, an Open Source Product Model
•Als KEY, PDF herunterladen•
2 gefällt mir•2,384 views
Empfohlen
Weitere ähnliche Inhalte
Andere mochten auch
Andere mochten auch (20)
Ähnlich wie Drupal Distributions, an Open Source Product Model
Ähnlich wie Drupal Distributions, an Open Source Product Model (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Drupal Distributions, an Open Source Product Model
- 1. Drupal Distributions, an Open Source Product Model Lev Tsypin lev@thinkshout.com ThinkShout.com
- 2. Agenda • Drupal basics • What are distributions? • Prominent examples • Business models
- 3. “Drupal is an open source content management platform powering millions of websites and applications”
- 4. Drupal is: • Core platform and modules • Contributed modules • Themes • Custom modules • Configuration • Community
- 5. What are Distributions? A collection of modules, themes, 3rd party libraries and settings that solve a specific problem.
- 6. Anatomy of a distribution • Drupal core • Installation profile • Modules • Themes • 3rd party libraries, E.g., OpenLayers, ImageMagick
- 7. What problems do distributions solve? • Bundling code, design, and configuration into a single package. • Downloading and configuring each dependency individually. • Eliminate the need to sift through the thousands of available modules.
- 9. Open Atrium • “Open Atrium is an intranet in a box” • Features include a blog, wiki, calendar, to do list, shoutbox, and a dashboard to manage it all. • Initially developed by Development Seed for the World Bank and then sold to Phase2 Technology.
- 10. • A social networking platform allowing organizations to interact with their constituents. • Feature set comparable to Jive and Facebook. • Developed by Acquia targeting the enterprise space
- 11. • Tailored for government websites • Enhanced security, accessibility, directory, and media room • Developed from the ground up by Phase2
- 12. Conference Organization • Distribution for creating a conference website • Features event signup, session proposals, voting / judging, scheduling, and social networking. • An example of a grass roots distro developed by and for the community.
- 13. • ThinkShout’s distribution targeting conservation groups • 35 known installs, 20 paid • Sites launched in a series of web sprints • Allows for innovative custom development while serving grass roots • Biggest challenge is maintenance
- 14. DEMO!
- 15. Building a distribution • Identify a need • Design features to meet it • Develop one or more themes • Build! • Market & Promote: release on d.o., marketing site, blog, nurture community
- 16. Business Models
- 17. Customization
- 19. Hosting
- 20. Revenue share with a publisher like Acquia
- 21. Lead generation
- 22. Challenges • Make distributions commercially viable • Fragmentation, E.g., debian vs ubuntu • Competing niche products dilute Drupal • Distributed communities shrink resources • Small core / Framework vs CMS
- 23. Questions? Lev Tsypin ThinkShout.com drupal.org/user/54135 @levelos
Hinweis der Redaktion
- \n
- \n
- Core platform\nContributed modules\nCustom modules\nThemes\nConfiguration\nCommunity\n
- \n
- \n
- \n
- \n
- \n
- Distros often built on the backs of Enterprise clients, E.g., Open Publish for Thomas Reuters and OpenAtrium for the World Bank\n
- \n
- \n
- Used by all DrupalCons and most Drupal camps\n
- Watershed Now is a Drupal distribution developed to support the common content management, social media, online advocacy, fundraising, and geo-mapping needs of conservation organizations. The goal of this project is to allow conservation organizations to quickly "boot up" effective, easy-to-use websites on an inexpensive web host in minimal time.\n\nUsed in US, Mexico, and Canada, people contacted us from as far away as Mirinmar and New Zealand\nWeb sprint model\ndeveloped based on client projects\nfoundation for customizations\ndo innovative custom development while still serving the grass roots\nmaintainability is a challenge once the site launches\n
- \n
- Focus a distro on a very specific vertical and/or use case, and make sure it's one you know well \n\nCommunity tips:- Good documentation\nRoadmap\nSpread the word beyond Drupal\n
- \n
- \n
- \n
- \n
- \n
- \n
- It takes lots of time and money to build a distro which organizations need to recoup. Distros as a lead gen tool is not scalable.\n\ndistros should be built to compliment core, not fight it\n
- \n