A few months ago I did a webniar for MadCap on my company’s move from Adobe FrameMaker to Flare. We made the move for a number reasons – lack of support for FrameMaker from Adobe, FrameMaker was starting to look and feel “old fashion – but our primary reason for the move was we needed the granular control offered in a topic-based authoring environment, and FrameMaker did not offer that.
The webinar focuses on the following:
- Overview of the migration process
- How we prepared our FrameMaker content
- The import process in Flare
- Cleanup required in Flare after the migration
- How implementing MadCap Flare increased Blackbaud’s content reuse/single sourcing and allowed us granular-level control of output at the paragraph, topic, TOC, and target levels
If you take the time to watch it, let me know what you think or if you have any questions. We are in the middle of moving another large chunk for FrameMaker content into Flare, so the process remains fresh in my mind.
2 responses to “Moving from FrameMaker to Flare”
Hi, I’m in the middle of evaluating Flare for my company – also to move over from Frame. Would you be willing to email about your thoughts on it?
I’d highly recommend moving from Frame to Flare. Flare is a far superior tool:
– Native XML
– Template driven
– Better format control
– True Topic-based authoring
– Output flexibility
– Import flexibility
It’s authoring environment is equal to that of Frame – intuitive and relatively simple to learn.
In addition, Flare makes moving content from FrameMaker into Fare pretty simple, and should you ever want to move this content back into Frame, that’s also a simple process.
Please let me know if you have any questions.