Technical Communication A to Z

Sounds like fun 🙂

Leading Technical Communication

Last week Stan Carey, editor and blogger, gave us his A-to-Z of linguistics.

In the spirit of paying homage to Stan’s marvelous work, or maybe just in the spirit of crass plagiarism, I now present Technical Communication A to Z.

A is for agile, with scrums and with sprints;
B is for books, if you like yours in print.

dita-bird_0C is for content, which some say is king;
D is for DITA, it’s still evolving.

E is for editors, some gentle, some crusty;
F is for FrameMaker, solid and trusty.

G is for Google, our path to Page One;
H is for help systems, show how it’s done.

Jekyll software logo

I’d rather be writing is what I is for;
J is for Jekyll, which techies adore.

K is for KPIs, things that we measure;
L is for L10N, always a pleasure.

M is for Madcap, performing with…

View original post 107 more words


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s