WebWorks ePublisher allows you to single source Adobe FrameMaker, Microsoft Word and DITA-XML content into web, PDF and online help deliverables. This presentation covers the following topics: o Overview of the WebWorks ePublisher platform and its architecture. o Overview of the WebWorks Help online help format. o Designing single sourcing templates using WebWorks ePublisher Pro. o Integrating the WebWorks ePublisher platform with a content management system to create an enterprise-level single sourcing and content publishing environment.

1. Single Sourcing with WebWorksePublisher Selvakumar T SCadence Design Systems

2. Agenda About Single Sourcing About WebWorksePublisher Platform Designing Single Sourcing Templates with WebWorksePublisher Pro Publishing Content Using WebWorksePublisher Platform Integrating WebWorksePublisher with a CMS

3. What is Single Sourcing? Using a single source document to create outputs: in different formats for different target audience

4. Why Single Source? Deliverables for multiple audiences in multiple formats Reduce duplication of content and tools Focus on content and not on format Need for automated publishing workflows Manage with reduced resources Faster time to market

5. FM Single Sourcing Tools In no particular order … WebWorksePublisher Platform http://www.webworks.com Mif2Gohttp://www.omsys.com/ Adobe RoboHelphttp://adobe.com

6. WebWorksePublisher Platform From Quadralay Corporationhttp://quadralay.com Platform Components: ePublisher Pro ePublisher Express ePublisher AutoMap

8. Input for WebWorks Adobe FrameMaker Microsoft Word DITA

9. WebWorks Output Formats HTML 3.2 XHTML 1.0 XML+XSL Wiki Markup (Confluence, MoinMoin and MediaWiki) WebWorks Help Microsoft HTML Help Microsoft WinHelp Eclipse Help Sun JavaHelp 1.1.3 or 2.0 Oracle Help PDF Microsoft Reader Palm Reader

10. WebWorks Help Runs on multiple platforms Full-text search, customized search, expand/collapse sections, browse and breadcrumb navigation, related topics, and a table of contents tree control WebWorks Help API for context sensitive help Publish content in a variety of ways: On a Web server On a network server available to multiple users through a share On the local computer where the application is installed On a CD-ROM

11. WebWorksePublisher Architecture Converts FrameMaker (.fm) files to Maker Interchange Format (MIF) Converts MIF files to XML Apply CSS stylesheets and XSL transforms to create HTML

12. ePublisher Workflow Create and deploy stationery using ePublisher Pro Use stationery to publish content with ePublisher Express or ePublisher Automap

13. Designing Single Sourcing Templates Create a project in ePublisher Pro Add FrameMaker files that use all possible types and styles of content Define styles and configuration to create stationery Deploy stationery and scripts

14. FM Source Requirements Paragraph and character format names should not include a period in their name. Use referenced images. Copied images will be rasterized and could lose clarity. 96 DPI preferred. ePublisher supports only .jpg, .gif, .png, and .svg files. ePublisherrasterizes all other formats. Custom marker types used to implement online features.

15. Customer Marker Types Several custom marker types used to implement online features. Keywords: Keywords to include in the meta tag for the topic --- for improving search. ImageAltText: Alternate text for an image. Popup*: Content to include in a popup window.

16. Variables and Conditions Combine variables and conditions to customize information for multiple versions of a product while reducing your maintenance costs by reducing duplicate information.

17. ePublisher Publishing Config

18. ePublisher Automap For automated publishing of content Supports GUI and batch mode

19. Integrating with a CMS Use FrameMaker Developer Kit (FDK) to develop interfaces to WebWorks Use FDK and CMS APIs to enable content management from the FrameMaker GUI

20. ThankYou