Making Wcm Easy With Alfresco Share 3 2


Published on

Slides from this week's webinar with the Blue Fish Development Group showing how easy web content management really is with Alfresco Share 3.2. Blue Fish have over 11 years experience of WCM and appreciate that organisations need different things from their CMS. Traditional websites need a CMS that is aimed at the business user - see just how easy this is with their Casual Contributor UI demo.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Making Wcm Easy With Alfresco Share 3 2

  1. 1. Making WCM Easy with Alfresco Share 3.2 February 18, 2010
  2. 2. Agenda 2 • Introductions & Housekeeping • The Myth of "One Size Fits All" WCM • Common WCM Challenges with Typical Web Sites • Using Alfresco Share to Address these Challenges • Demonstration • Q&A
  3. 3. Introductions 3 • Michael Trafton – Chief Architect, Blue Fish Development Group • Joshua Toub – General Manager, Blue Fish Development Group
  4. 4. Who the heck is Blue Fish? 4 • Blue Fish has been singularly focused on ECM for 11 years • Primarily in the areas of: • Web Content Management • Document Management • Custom Application Development • Full lifecycle projects (cradle to grave) • Alfresco expertise in "Small Bites"
  5. 5. The Small Bites Menu 5 Quick Start Package • Appetizers • Alfresco Sandbox • Alfresco Requirements Workshop • Alfresco Evaluation • Alfresco System Architecture • Alfresco Solution Design • Alfresco Sandbox • Alfresco Configuration • Entrées • Alfresco Requirements Workshop • Alfresco Architecture Review • Alfresco System Architecture • Alfresco Solution Design from $2,500 • Alfresco Configuration to $20,000 • Alfresco Customization and Development • Dessert • Migrating Documents into Alfresco
  6. 6. Myth of "One Size Fits All" WCM
  7. 7. WCM Myths 7 • We often hear WCM vendors say that their product is a good fit for any and all WCM projects… • …but that's not what we've seen out in the field • Sometimes, WCM really streamlines web site production • Other times, WCM makes it much harder to do your job • Why is that?
  8. 8. Different Types of Sites 8 Leading Edge Web Sites Traditional Web Sites • Volatile – Look & Feel Changes Frequently • Stable – Look & Feel Only Changes every • Innovative - Ajax, Flash used for User 3-5 Years Interface, eCommerce and other • Conventional – HTML, CSS, Flash used Applications for Eye Candy • Diverse – Multiple Sites with Different • Homogenous – Consistent Visual Design Visual Themes Throughout
  9. 9. Different WCM Needs 9 Leading Edge Web Sites Traditional Web Sites • Flexibility • Contribution by Business Users • Rapid Time to Market • Enforce Consistency of Look and Feel • Easy to Test, Easy to Change • Repurpose Content Across Multiple • Changes to Several Files at Once Platforms or Sites • Avoid Stepping on Other Developers' Toes • Reduce Time and Effort for Future • Rollback Things that Didn’t Work Rebranding Leading Edge Web Sites Traditional Web Sites need a CMS aimed at need a CMS aimed at Web Developers Business Users
  10. 10. Where Does Alfresco AVM Fit? 10 • Alfresco AVM is great for Leading Edge web sites • Manage and deploy code and web content together • Sandboxes let users work on lots of connected files in a protected area • Submit a collection of changes that go live together • File System-based UI (CIFS) allows easy use of HTML/code editors • Snapshots allow large sets of changes to be rolled back • This flexibility and power can be overwhelming for traditional sites • Can we tweak Alfresco to be a better fit for traditional sites?
  11. 11. Common WCM Challenges for Traditional Sites
  12. 12. We Often Hear… 12 • User Adoption is low • People still email their content to the web team in MS Word • New users struggle to use the system • They were not part of the initial training • Infrequent users struggle to use the system • The training "wore off" • IT team is still too involved • We're not getting the ROI we wanted
  13. 13. Why Is This So Hard? 13 • Need more focus on the “Casual Contributor” role • Web content is not their job • It's extra work on top of their normal job • They aren't web savvy • Not designers, don't know HTML • They don't know about WCM • and they don't care – they just want their content on the web site • You can't train them • There are too many of them, too far away, etc. • They hardly ever contribute content • There's no reinforcement • An Intuitive User Interface is Key
  14. 14. What We've Done Using Alfresco Share as a WCM Platform for Traditional Web Site
  15. 15. Key Points About Our Solution 15 • Site Designed by Developers, Maintained by Business Users • Similar to popular blogging software • You decide what the web site is going to look like, then create forms that allow authors to enter content that conforms to the site's design • Content as a Service Pattern • Web site consumes content from Alfresco • Separates WCM expertise from Web Site Expertise • Particularly useful in Portals, Intranets, E-Commerce Sites, Environments with high reuse, Environments with multiple technologies • Different UIs for Casual Contributors and Approvers • Approvers are typically the "web team" • Focused on the web – they "get it" • Overworked, need as much help/automation as they can get • Don't have time to spend making author's pages pretty • Approvers can deal with a more typical WCM UI
  16. 16. Casual Contributor UI 16 • Integrated with the web site • Web site IS the user interface • Intuitive and Bullet Proof • Requires Zero Training • Wizards and Forms • Guides authors through the process • Eliminates mistakes • Power Users would revolt, casual users love it
  17. 17. Casual Contributor UI Demo
  18. 18. Approver UI 18 • Built on Alfresco Share • Uses same forms as Casual Contributor UI • Makes approval easy • Provides more control for advanced users • Copy/Move files • Control permissions • Retire/Expire files • Advanced search • etc.
  19. 19. Approver UI Demo
  20. 20. Architecture 20 • Built on Alfresco DM • UI Built Using Components from Alfresco Share • Forms Service for Web Page Templates • Content as a Service • Web Site requests content from Alfresco via RESTful APIs • Content Fragments, Queries, Full-Text Search • Simple Workflow for Approval Portal Requests Navigation • Email Notifications eliminates need to log in and check an "inbox" Web Site Alfresco CMS Portal Requests Content or Portal Portal Issues Searches • Folder Actions Author Approver • Attaching aspects, object types, and workflows Portal User Requests Creates/Edits Approves Web Page in Browser Content Content • Automatically filing content based on attribute values • Sending Email Notifications Author Approver Portal User • "Lifecycle" States for Effectivity and Preview
  21. 21. Questions? Michael Trafton Josh Toub