5/2/2014 Footer 1
MIGRATING FROM FRAMEMAKER TO
FLARE: PREPARATION AND
PROCESSES
By Denise Kadilak
Information Architect/Te...
5/2/2014 Footer 2
ABOUT ME
Information Architect/Team Lead with Blackbaud, Inc.
16 years experience
Varied responsibilitie...
5/2/2014 Footer 3
BACKGROUND
After 11 years working in Adobe FrameMaker
(five of those years in structured FrameMaker)
Bla...
5/2/2014 Footer 4
BACKGROUND
Over an 18-month period, we:
 Created a Flare testing team
 Tested Flare
 Authoring enviro...
5/2/2014 Footer 5
BACKGROUND
Over an 18-month period, we:
 Implemented a migration process
 Created the necessary templa...
5/2/2014 Footer 6
MAKING THE MOVE
1. Prepare FrameMaker content
2. Create Flare import
3. Clean content imported to Flare
...
5/2/2014 Footer 7
PREPARE FRAMEMAKER CONTENT
 Remove unused formats
 Remove unused conditions
 Remove style overrides
...
5/2/2014 Footer 8
PREPARE FRAMEMAKER CONTENT
 Generate book updates in FrameMaker
 Update TOCs
 Confirm content can be ...
5/2/2014 Footer 9
PREPARE FRAMEMAKER CONTENT
 Create a “master” file that contains all
formats you want to include in you...
5/2/2014 Footer 10
PREPARE FRAMEMAKER CONTENT
 Set Adobe Distiller Settings:
Flare uses Distiller to convert graphics
I...
5/2/2014 Footer 11
SAMPLE SCREEN
Distiller XI
5/2/2014 Footer 12
CREATE AN IMPORT TEMPLATE
 Save import definitions
 Create a new project
 Import the “master” Frame ...
5/2/2014 Footer 13
CLEAN IMPORTED CONTENT
 Topics and images import to one folder
 Output content mirrors Content Explor...
5/2/2014 Footer 14
CLEAN IMPORTED CONTENT
 Define any formats missed during import
 Create mediums for each output need
...
5/2/2014 Footer 15
CLEAN IMPORTED CONTENT
 Master Pages (online content)
 Page Layouts (print content)
 Snippets
 Tabl...
5/2/2014 Footer 16
CLEAN IMPORTED CONTENT
 TOC
 Variables
 Targets
 Conditional Text
 Skins
Create/edit project files
5/2/2014 Footer 17
SUGGESTION
 Condition tag set
 Images
 Master Page (breadcrumbs, mini proxy)
 Page Layout (show our...
5/2/2014 Footer 18
SUGGESTION
 We used a Wiki
 Import process
 Working in Flare
 Globally link projects
 Template Ins...
5/2/2014 Footer 19
PROBLEMS
 Binding to Team Foundation Server
 Stylesheet Editor awkward
5/2/2014 Footer 20
CONCLUSION
 Flare is a great tool with a lot of options
 It can overwhelm you
 Leaning it involves l...
5/2/2014 Footer 21
5/2/2014 Footer 22
5/2/2014 Footer 23
QUESTIONS?
denise.kadilak@blackbaud.com
My contact information:
Upcoming SlideShare
Loading in...5
×

Moving Content from FrameMake to Flare

201

Published on

Takes you through the process of moving content from Adobe FrameMaker to MadCap Flare: preping the content, importing content, and cleaning content after the import.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
201
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Moving Content from FrameMake to Flare

  1. 1. 5/2/2014 Footer 1 MIGRATING FROM FRAMEMAKER TO FLARE: PREPARATION AND PROCESSES By Denise Kadilak Information Architect/Team Manager
  2. 2. 5/2/2014 Footer 2 ABOUT ME Information Architect/Team Lead with Blackbaud, Inc. 16 years experience Varied responsibilities Creating and maintaining 1000s of pages of user-end documentation Technical-project lead investigating new tools, best practices, and workflows for a 22-member documentation team Led team’s move four years ago to MadCap Flare Past presentations: Agile-based development process at the 2010 WritersUA Conference Structured authoring, trends in Technical Communication, and indexing at various local and international STC conferences Part-time instructor at John Carroll University in Cleveland, OH Teach the Technical Writing course included in the school’s Professional Writing program
  3. 3. 5/2/2014 Footer 3 BACKGROUND 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. Why we moved
  4. 4. 5/2/2014 Footer 4 BACKGROUND Over an 18-month period, we:  Created a Flare testing team  Tested Flare  Authoring environment  Workflow options  Output options  HTML-based online help  PDF print How we moved
  5. 5. 5/2/2014 Footer 5 BACKGROUND Over an 18-month period, we:  Implemented a migration process  Created the necessary templates Moved content How we moved
  6. 6. 5/2/2014 Footer 6 MAKING THE MOVE 1. Prepare FrameMaker content 2. Create Flare import 3. Clean content imported to Flare Three primary steps
  7. 7. 5/2/2014 Footer 7 PREPARE FRAMEMAKER CONTENT  Remove unused formats  Remove unused conditions  Remove style overrides  Additional steps if in structured FrameMaker  Convert attributes to conditions  Change x-ref source type  Fix broken x-refs  FrameScripts are a big help Clean existing documents
  8. 8. 5/2/2014 Footer 8 PREPARE FRAMEMAKER CONTENT  Generate book updates in FrameMaker  Update TOCs  Confirm content can be chunked into stand- alone topics  Five steps from legacy documentation to topics Confirm existing content is ready to import
  9. 9. 5/2/2014 Footer 9 PREPARE FRAMEMAKER CONTENT  Create a “master” file that contains all formats you want to include in your Flare css. Confirm existing content is ready to import
  10. 10. 5/2/2014 Footer 10 PREPARE FRAMEMAKER CONTENT  Set Adobe Distiller Settings: Flare uses Distiller to convert graphics Important to get your settings correct I created a “Flare” Settings option in Distiller In Images, set Downsampling to Off or None to prevent pixel reduction in graphics Confirm existing content is ready to import
  11. 11. 5/2/2014 Footer 11 SAMPLE SCREEN Distiller XI
  12. 12. 5/2/2014 Footer 12 CREATE AN IMPORT TEMPLATE  Save import definitions  Create a new project  Import the “master” Frame file you created Options tab (page 26) – you’ll need this later. Flare’s Import Wizard
  13. 13. 5/2/2014 Footer 13 CLEAN IMPORTED CONTENT  Topics and images import to one folder  Output content mirrors Content Explorer structure Arrange topic and image files
  14. 14. 5/2/2014 Footer 14 CLEAN IMPORTED CONTENT  Define any formats missed during import  Create mediums for each output need  Print  Online  Mobile Edit CSS created during import process
  15. 15. 5/2/2014 Footer 15 CLEAN IMPORTED CONTENT  Master Pages (online content)  Page Layouts (print content)  Snippets  Table Styles Create additional resource files
  16. 16. 5/2/2014 Footer 16 CLEAN IMPORTED CONTENT  TOC  Variables  Targets  Conditional Text  Skins Create/edit project files
  17. 17. 5/2/2014 Footer 17 SUGGESTION  Condition tag set  Images  Master Page (breadcrumbs, mini proxy)  Page Layout (show ours)  Stylesheet (anything unique or invonvated) Create a template project and use global project link
  18. 18. 5/2/2014 Footer 18 SUGGESTION  We used a Wiki  Import process  Working in Flare  Globally link projects  Template Instructions  Notes and Issues  Tips and Tricks Create internal documentation
  19. 19. 5/2/2014 Footer 19 PROBLEMS  Binding to Team Foundation Server  Stylesheet Editor awkward
  20. 20. 5/2/2014 Footer 20 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 methodical
  21. 21. 5/2/2014 Footer 21
  22. 22. 5/2/2014 Footer 22
  23. 23. 5/2/2014 Footer 23 QUESTIONS? denise.kadilak@blackbaud.com My contact information:
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×