Downloaded 63 times
Uploaded byDave DeMichele
Liferay v. Drupal: Pound for Pound @ Liferay Symposium 2014 - Findings from the Yale Hub POC project
The document presents a proof of concept for 'The Hub' project at Yale University, comparing Drupal and Liferay as portal frameworks. It details the development process, user story completions, and delivery methods used for both platforms, revealing that Drupal completed more user stories than Liferay. The project aimed to create a user-friendly, integrated online experience that centralizes tools and technologies while being mobile accessible.
![[DevDay2018] Liferay DXP – A powerful Enterprise Solution - By Vy Bui, Develo...](https://cdn.slidesharecdn.com/ss_thumbnails/f109-buithevy-liferaydxp-apowerfulenterprisesolution-180419095507-thumbnail.jpg?width=640&height=640&fit=bounds)
Liferay v. Drupal: Pound for Pound @ Liferay Symposium 2014 - Findings from the Yale Hub POC project
- 1. Drupal vs. Liferay:Pound for Pound All things being equal, inequality reigns Dave DeMichele Application Architect, Yale University Andrew Gruhn Solution Architect, sdg
- 2. Slide Topic SlideInfo • Bullet 1 • Bullet 2 • Bullet 3 #LRNAS2014
- 3. The Hub ProjectProof of Concept #LRNAS2014
- 4. The Hub ProjectProof of Concept – Yale Information Technology Solutions The Hub Vision • Build an easy-to-use, contextual, collaborative, inter-connected online experience • Focus on centralizing tools and technologies • “Presentation” Layer Platform • Theming via HTML & CSS • Highly configurable and Mobile accessible • Targeted content by role(s) • Widgets / code blocks • Communities and social • Blogs, micro-blogging, forums • Internal & external system integration • Federated Authentication • Cloud-based hosting #LRNAS2014
- 5. The Hub ProjectProof of Concept – Yale Information Technology Solutions Process • Researched technological options that fit requirements • Determined that a portal framework was desired • Finalists • Salesforce • Sharepoint • Drupal • Exo Platform • Liferay #LRNAS2014
- 6. The Hub ProjectProof of Concept – Yale Information Technology Solutions The Bake-off #LRNAS2014
- 7. The Hub ProjectProof of Concept – Yale Information Technology Solutions The Bake-off • Six week development on two platforms • Hired firms for Drupal and Liferay • Four Kitchens, Austin TX • sdg, Minneapolis MN • Defined 62 user stories • UI/UX Assessment • Integrations with 3rd party apps • Force.com • ServiceNow #LRNAS2014
- 8. The Hub ProjectProof of Concept – Yale Information Technology Solutions The Results #LRNAS2014
- 9. The Hub ProjectProof of Concept – Yale Information Technology Solutions Number User Stories Completed by Platform 65 60 55 50 45 40 35 30 25 20 15 10 5 0 #LRNAS2014 1 Total User Stories Drupal Completed Stories Liferay Completed Stories 1 35 25 3 2 8 9 9 2 3 62 1 20 2 9 1 2 25 2 2 7 6 9 2 3 55 Count of User Stories User Story Features
- 10. 55 50 45 40 35 30 25 20 15 10 5 0 #LRNAS2014 Drupal Dev Hrs (54.57 Total) Platform Development Hours Liferay Dev Hrs (23.33 Total) 8.25 10 26.99 2 3.5 0.5 1 0.5 11 3.08 0.75 2.25 4.08 4 by Feature Widgets User Exp Target Content Social Collaboration Personalization Mobile Access Consume Feeds Communities Activity Streams The Hub Project Proof of Concept – Yale Information Technology Solutions
- 11. Drupal Delivery Methodof Completed Stories #LRNAS2014 Documentation 46% Out-of-Box 43% Configuration 14% Development 23% Liferay Delivery Method of Completed Stories Out-of-Box 27% Configuration 65% Configuration & Development 4% Development 4% The Hub Project Proof of Concept – Yale Information Technology Solutions
- 12. The Hub ProjectProof of Concept – Yale Information Technology Solutions Questions? #LRNAS2014
- 13. The Hub ProjectProof of Concept – Yale Information Technology Solutions Andrew Gruhn Solution Architect, sdg andrew.gruhn@solutiondesign.com 612-961-4208 Dave DeMichele Application Architect, Yale University dave.demichele@yale.edu 203-436-5775 #LRNAS2014
Editor's Notes
- #3 Branford College
- #5 Yale is decentralized – 100s of departments that like to operate independently Work Layer also explored – force.com
- #6 Ranked technologies against each core requirement multiple times throughout process Choose which to move forward with product demos - Spent time convincing ourselves that this wasn’t a portal Portal framework decision eliminated most Drupal kept in because of large footprint on campus and expensive support/development team in ITS
- #8 4 – 1 week sprints… not recommended but no choice - self-imposed time constraints Originally had 90+ user stories UI/UX and security assessments done Chose force.com (chatter) and servicenow to test integration pieces.
- #10 Note: 4 kitchens smaller team than sdg so this slide doesn’t tell the whole story. However…
- #11 This slide does – it took twice as much time to build out the same functionality with Drupal Commons than Liferay
- #12 Yale ITS doesn’t want to be in the coding business when it can be avoided. We want to build with clicks, not code. Configuration can be done by technical staff, but not necessarily programmers. Important distinction. End result: Liferay is we were ready for a commitment to the Hub vision, Drupal for a short-term stop gap.