If you have a list of phrases (e.g. a list of STE terms) you would like to quickly add to Flare as snippet files to make good use of Flare’s clever “auto suggest based on snippet” feature, keep reading.
Yep, we’re doing it again. MadWorld returns to the Hard Rock Hotel San Diego April 13-15, 2014 and you’re invited to join the “Mad”ness! MadWorld 2014 is the premier technical communication and content strategy conference for technical writers, documentation managers and content strategists.
Software trends seem to change as often as I change my socks. The latest buzz has developers pushing for implementing Git source control. Right now Flare has a plug in for a few source control options, but when your company goes in a different direction, it may leave you scratching your head. So, recently I made the move to Git. Not gonna lie, it was a bit painful at first. But after a few missteps, I got Git going. Here are a few points I can share that may ease the pain…
“If you could start your docs from scratch, what formats would you be delivering & what documentation infrastructure would you be building?” This was the question that kicked off a lively discussion in the Documentation and Technical Writing Management group on LinkedIn.
We often see customers looking to adopt Flare who already have an existing software system or website they'd like to integrate with their Flare output. The good news is, this can be easily done. Your options include, 1) linking to the Flare generated content from your existing site or intranet or, 2) by embedding the Flare output entirely or by using the compiled xhtml pages to be imported or displayed by another application/system.