Content Management System and Portal

1. Content Management System and Portal

2. Contents • Portal Overview • Introduction to WCM • WCM Best Practices

3. Weather PORTAL Checking Savings News This illustration depicts a page aggregating data and content - account balances, weather report, and news - provided by different sources. What Is A Portal? “Portal” refers to an application that serves to aggregate content, data, and services coming from multiple sources presented in a usable way through single, consistent user interface.

4. Checking Weather PORTLET PORTLET What Is A Portlet? Portlets are web components that have special properties to allow them to easily plug into and run in enclosing applications like portals. • Equivalent to components in the portal world • Include presentation logic and represents a self-contained modular functionality of an application • Interacts with the business layer components • Designed to be aggregated in the larger context of composite pages • Have data, content or links to applications, which are integrated either through a Simple or Complex integration (in later slides)

5. Portal Page Portals aggregate various applications into a dashboard and provides unique opportunity to offer value added services and become more than sum of these applications. Links leading to customization pages for showing/hiding different entitlements, editing company information (available to privileged users only), changing layout of certain modules (others are locked down), changing certain user level preferences, etc. High level navigation is totally controlled by the portal. Finer application level navigation is the application’s responsibility (for loosely coupled applications only). welcome message – preferably with the user name/role and company name Role based applications Application level customization links Cross Sell ‘white space’ populated using personalization rules.

6. Portal Benefits • Consistent enterprise view • A familiar user interface and information architecture brings together existing web sites, databases, and other applications into a single gateway, enabling faster decision-making and better-equipped customers and employees. • Customer and Employee satisfaction and retention • Providing personalized information to online users frees them from the avalanche of information. • Enhanced Decision making • Portals can make it easier for employee teams, customers, partners and other principals to work together. • They also provide an increased capability to "push" communications of lessons learned, new policies, etc., to the right people. • Continuous Improvement • The ability to identify and track portal usage at both a organizational level and an individual level enables business owners to gather information about the behavior and habits of users, so the offering can be improved over time. • Cost Reduction • Reduced support and training cost via self service • Revenue Enhancements • Allows an ability to cross sell • Faster time to market

7. Contents • Portal Overview • Introduction to WCM • WCM Best Practices

8. Why WCM (Web Content Management) • Information Overload – In the next 2 years more original content will be created than in all of prior human history. • Organizations need the right information to get to the right people at the right time, so that their websites are efficient and effective. • Content Management Solutions: • Reduce webmaster bottleneck • Allow non technical business users control over THEIR web content • Provide Workflow for management of content • Provide Personalization that effectively targets content. WCM INCREASES ROI & REDUCES TCO ON WEB INITIATIVES

9. IBM Workplace Web Content Management (IWWCM) • IBM Workplace Web Content Management provides a complete web content management solution • Enables business users to manage and control web site content • Separation of content from presentation • Facilitates content reuse and repurposing

10. IBM Web Content Management • WCM provides portlets for delivering content and components through Portal • WCM integrates with Personalization Server • Personalization rules use WCM Content • Personalization content spots/rules in WCM Templates • WCM can leverage document-centric content • Integrates with the Portal Document Manager (5.1) • WCM can leverage content in the enterprise • Integrates with DB2 Content Manager

11. WCM Features • Component Based Architecture • Easy Content Creation for non technical users • Site Map Management • Taxonomical based Navigation • Separation of Content from Presentation • Intelligent Components

12. Basics of Web Content Management

13. Web Content Management Life cycle The six steps in the life cycle are: • Create: content is created or revised, resulting in a new version of content to be managed by the repository. • Review: A critical stage to getting content approved is first having it reviewed within the organization. The review and approval process may use workflow technology to facilitate comments and changes to the content. The result is the promotion of content to an approved stage. • Aggregate and manage: Approved content is stored and managed in the repository. Content is available for aggregation and reuse in other contexts. • Distribute: Content is available for access and distribution. Access can be accomplished directly from the repository or through ancillary applications. Content distribution is formatted for the specific output device or targeted market. • Archive: Information is archived based on a set of rules that specify the time in which the content is considered to be valid or accurate. An active repository can automatically delete expired content or present it to a manager for review. • Destroy: When content is no longer valuable to an organization, it may be destroyed. Some content may not be destroyed but will be reused or integrated with other content, thus starting the life cycle again.

14. Web Content Management – Benefits Technology Benefits Business Benefits • Standard templates • Ease of use • Separates content from Presentation • Allows re-branding from same data • Content syndication • Database driven • The work is always backed up • Disaster Recovery • Archiving and versioning helps in recovering last working version of the content • Expedites publishing process • via workflow capability • Shared environment • Lowers cost by virtue of shared components, re-usable content, cost effective co-branding • Dynamic delivery • Simply putting documents online, whether on the Internet, an intranet, or an extranet does not make content reusable and useful • Content is to be developed and stored in small enough units that it can be leveraged among many different deliverables • Source of content can be used in many ways to meet the needs of many different people • Reinforces branding • Common look and feel • EnsureRegulatory Compliance • SOX, HIPPA • Reduces time to market • Workflow features helps automate, streamline, and enforce controls on creation • Decentralizes publishing • Business users can publish without IT involvement • Improves Employee Productivity • Optimize costs associated with storing and retrieving documents

15. Web Content Management Process Content Management system should automate all the steps involved in publishing information on the website. It will empower business users to manage content without technology intervention. • Content contributors can create content using the authoring interface – all creation should be ‘controlled’ by a use of templates • Templates support a consistent look and feel, promote the reuse of design elements, and make it easy for non-technical users to contribute content to the site. • Presentation templates allow isolation of presentation (UI, navigation) from information • Data templates allow isolation of content structure from information.

16. The content management process

17. Contents • Portal Overview • Introduction to WCM • WCM Best Practices

18. Best Practices • Leverage Metadata as much as possible • People First – Content Management is about people – not just content • Control Access to Content • Support rich searching • Automate costly and time consuming processes • Templates • Leverage existing assets and skills as much as possible • Support existing co-operate standards • Leverage exiting corporate directory • Separate content from presentation • Choose number of contributors wisely • Address globalization and localization issues • Streamline the existing authoring/review process. • Build Flexible Workflows • Build error checks and use ‘web view’ to validate content • Establish clear ‘contract’ between the CMS and portal • Inventory of assets and their metadata • Content delivery architecture • Dynamic and static asset integration mechanism • Implement plans for archiving content over time • Keep Content timely

19. WCM Best Practices • Consistent Presentation • Effective Site Structure • Effective Content Structure • Consistent Navigation • Taxonomies and Categorisation • Good Quality Content • Well Managed Content • Content in Portal

20. 1. Consistent Presentation This is important for: • Branding • Sense of place • Clarity • Keeps the responsibility of designing presentation away from the Content Creator

21. 1. Consistent Presentation: Dynamic Component Architecture

22. 1. Consistent Presentation: Presentation Templates • Used to display an item of content as a web page • Presentation Templates contain: • Markup (HTML) • Components: • Navigation from sitemap • Menus for serendipitous links • Presentation components for re-use • Can show a subset of the content • Presentation Templates are secure for field level security

23. 1. Consistent Presentation: Components • Easy reuse of elements • Static for shared elements such as branding • Dynamic for: • Navigation • Related links • Personalisation • Component Types • Text, Rich Text, HTML • File Resource, Image Resource, Document Resource • Menu, Navigator, Taxonomy

24. 2. Effective Site Structure • The structure of the site must be: • Intuitive • Customer focused • WCM facilitates this: • Easy to manage site framework, tree control • Content can sit in multiple site areas • Meta information to be combined with content • Automatically used to generate the navigation for the site

25. 2. Effective Site Structure

26. 3. Effective Content Structure • This means that content split into meaningful fields, not a large block of content. • It is easier for content creators • It allows consistent presentation of information • Allows easy reuse of content, in different sites and for different devices.

27. 3. Effective content structure

28. 3. Effective content structure

29. 4. Consistent Navigation • Users have a sense of place • Users of the site never surprised • Consistent • Always up to date

30. 4. Consistent Navigation: Navigator Component • Provides a visual representation of the sitemap • Automatically generated from Sitemap • This important because it enforces consistent navigation across site

31. 5. Taxonomies & Categorisation • Content has structure beyond the navigational structure • Hierarchical Categories • All content is categorised • Navigation can be from categorisation as well as Site Map • Related Links / Serendipitous Links

32. 5. Taxonomies & Categorisation

33. 6. Good Quality Content • This is key to any site, WCM cannot create good content, but it can facilitate the process of creating it. • Content Originator should be content creator • Simple Browser based content entry • Content based on pre defined templates • Versioning

34. 7. Well Managed Content • Content has clear ownership • Is version controlled • Has an approval workflow and history • Secure • Meta data

35. 7. Well Managed Content: Workflow • The workflow controls: • How an item of content is published • The security permissions the published item has • All content must go through a workflow • A workflow can control: • Read • Edit • Approve/Decline • Delete • Live (ie. View on the web)

36. IWWCM with WebSphere Portal & Workplace • IWWCM provides the easiest way for end-user to publish content to Portal. • IWWCM key part of Workplace. • Portals and content management go hand-in-hand

37. Information Architecture • Site Map • Wire-frames • Process flow diagrams • Mock-up screens • Graphics • Content decks • UI Prototype • Customer Interview and Feedback • HTML fragments as per portlets • Style Sheets • Updates / fixes Usability Testing HTML Development UI creative Design Information Architecture UI Support UI Track Architecture Development Track Business Requirements Establishing the Business Case Hi Level Design Detailed Design Development / Integration Customer QA /Acceptance Deployment & Support Activities • Who is the audience? • What is the offer? • ROI for the Portal • Prioritization of functionalities required • Stakeholder Interviews • Iterative Activity to arrive at business requirements • Chalk out a high level Architecture • Content Inventory • Site Definition • UI decomposition and Portlet Identification • Application Design Mapping (MVC and other standards) • Deployment Strategy • Migration Plan • Content Migration • Build Approach – from site skeleton to portlets • Integration of ext. applications & infrastructure component such security, CMS, as applicable • Load testing • Customer testing phase • Bug-fixes • Post Deployment Support • Training / Knowledge Transfer Source: Mphasis Corporation Proof of Concept • Bug reports • Load Test Scripts and Reports Deliverables • Statement of Work • Business Case Document • ROI Analysis • Feature Value Analysis • Business Requirements • Use Cases • Technical Architecture Document • Portlet Identification Document • Overall Design Document • Class Diagrams • Detailed design for portlets • Migration, production rollout Plan • Development and Test Environment • Deployment plan • Code • Test Plans (Unit and Integration) • Test Scripts • Deployment plans and scripts • Code Review reports Portal Development Process

38. Requirement Gathering Activities Understanding the detail requirements of CE Money UK’s content creation and deployment processes