• Save
FrameMaker to Flare
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

FrameMaker to Flare

on

  • 1,013 views

Problems and process considerations when making the move from Adobe FrameMaker to MadCap Flare

Problems and process considerations when making the move from Adobe FrameMaker to MadCap Flare

Statistics

Views

Total Views
1,013
Views on SlideShare
1,012
Embed Views
1

Actions

Likes
0
Downloads
0
Comments
0

1 Embed 1

http://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • TITLE SLIDE.

FrameMaker to Flare Presentation Transcript

  • 1. ADOBE FRAMEMAKER TO FLARE Process and problems By Denise Kadilak Information Architect3/10/2013 Footer 1
  • 2. BACKGROUND Why we moved After 11 years working in Adobe FrameMaker (five of those years in structured FrameMaker) Blackbaud decided the increasing demands on the documentation team (content shared between six overlapping product lines) required a move to a topic-based environment.3/10/2013 Footer 2
  • 3. BACKGROUND How we moved Over an 18-month period, we:  Created a Flare testing team  Tested Flare  Authoring environment  Workflow options  Output options  HTML-based online help  PDF print3/10/2013 Footer 3
  • 4. BACKGROUND How we moved Over an 18-month period, we:  Implemented a migration process  Created the necessary templates  Created a Flare workflow  Moved content3/10/2013 Footer 4
  • 5. MAKING THE MOVE Three primary steps 1. Prepare FrameMaker content 2. Create Flare import 3. Clean content imported to Flare3/10/2013 Footer 5
  • 6. PREPARE FRAMEMAKER CONTENT Clean existing documents  Remove unused formats  Remove unused conditions  Additional steps if in structured FrameMaker  Convert attributes to conditions  Change x-ref source type  Fix broken x-refs  FrameScripts are a big help3/10/2013 Footer 6
  • 7. PREPARE FRAMEMAKER CONTENT Confirm existing content is ready to import  Confirm content can be chunked into stand- alone topics  Determine how to handle duplicate content  Consider creating “global” content from any text insets3/10/2013 Footer 7
  • 8. CREATE AN IMPORT TEMPLATE Flare’s Import FrameMaker Wizard  Save import definitions  Import books or individual files  Option to link generated files to source files  Determine how to chunk existing content3/10/2013 Footer 8
  • 9. CREATE AN IMPORT TEMPLATE Flare’s Import FrameMaker Wizard  Create a new or associate the project with an existing CSS  Confirm/update paragraph style mapping  Confirm/update character style mapping  Confirm/update x-ref style mapping3/10/2013 Footer 9
  • 10. CLEAN IMPORTED CONTENT Arrange topic and image files  Topics and images import to one folder  Output content mirrors Content Explorer structure3/10/2013 Footer 10
  • 11. CLEAN IMPORTED CONTENT Edit CSS created during import process  Define any formats missed during import  Create mediums for each output need  Print  Online  Mobile3/10/2013 Footer 11
  • 12. CLEAN IMPORTED CONTENT Create additional resource files  Master Pages (online content)  Page Layouts (print content)  Snippets  Table Styles3/10/2013 Footer 12
  • 13. CLEAN IMPORTED CONTENT Create/edit project files  TOC  Variables  Targets  Conditional Text  Skins3/10/2013 Footer 13
  • 14. SUGGESTION Create a template project and use global link  Condition tag set  Images  Master Page  Page Layout  Stylesheet3/10/2013 Footer 14
  • 15. SUGGESTION Create internal documentation  We used a Wiki  Import process  Working in Flare  Globally link projects  Template Instructions  Notes and Issues  Tips and Tricks3/10/2013 Footer 15
  • 16. PROBLEMS  Binding to Team Foundation Server  Stylesheet Editor awkward  No control over “Contents” output structure  Limited reporting functionality3/10/2013 Footer 16
  • 17. CONCLUSION  Flare is a great tool with a lot of options  It can overwhelm you  Leaning it involves lots of trial and error  Flare customer support very helpful  Know that this is going to take time  Be methodical3/10/2013 Footer 17
  • 18. QUESTIONS? My contact information: denise.kadilak@blackbaud.com3/10/2013 Footer 18