Adobe Products Technical Writer

Adobe for Technical Writing

If you are using Adobe products for your documentation and need a technical writer, give me a call.

Although I predominantly use other tools, I have worked with FrameMaker and InDesign, and also use Illustrator for creating images. I know my way around the tools and can use them to create user guides to meet your needs.

During my career, I’ve used:

  • Adobe FrameMaker (unstructured) – I wrote in FrameMaker for 10 years, creating user manuals which were published as PDF and converted to mif and then HTML.
  • Adobe InDesign – have used on a small number of projects for creating user guides and tutorials, delivered as PDF
  • Adobe Illustrator – Use quite regularly for creating simple diagrams and graphics
  • Adobe Captivate – Know how to use, but haven’t used those skills professionally (to date).

I haven’t used the structured version of Adobe FrameMaker, but I understand the concept of structured text (Paligo uses structured text). I have written in XML and am quite happy to brush up on structured FrameMaker before starting your project.

The images below show a sample of a document I created in InDesign.

Craig Wright

Craig Wright

Technical Writer

Example of User Guide in Adobe InDesign

Adobe InDesign Technical Writer
Adobe InDesign Technical Writer

Technical Writing in Adobe FrameMaker

If you’ve seen my profile page, you’ll know that I worked for many years as an employee for Serck Controls (which was eventually taken over by Schneider Electric). For the vast majority of my time there, I used Adobe FrameMaker for creating content. So if you use FrameMaker and need an extra pair of hands, I’ll be able to get to grips with your user guides quickly. 

Unfortunately, I can’t show any examples of the work I did in FrameMaker in great detail due to non-disclosure agreements. But the user guides were a fairly standard layout and used styles for consistency. Pretty much what you would expect from a manual.

When writing content in FrameMaker, I take the same sort of approach as when writing topic-based documentation. Each section is ‘stand-alone’ with references to other sections, rather than a reliance on the end-user having read ‘earlier’ sections. This is just good practice, and makes it a lot easier to convert to topic-based systems too.

Get in Touch.

If you have a question about technical communication or would like to know more about my technical writing services, please get in touch.

Contact Straygoat
Share This