Thanks for a great community
Celebrate our community by reading these great articles and interviews and articles from our first six months.
Today is US Thanksgiving, a day to gather with friends and family. On this day, we wanted to reflect on the great community we are fortunate to have at Technically We Write, and thank you for being with us.
We are thankful for our writer community who have shared so many great articles on the website. We are also thankful for our reader community who visit with us. And we are also thankful for those we interview about their role in technical communication. "Community" takes many forms, and we celebrate all of our community at Technically We Write.
Thanks for writing with us
At Technically We Write, we love to highlight technical writing, technical editing, and all forms of technical communication. And we love that so many of you have shared your tips, how-tos, and advice about technical communication, including technical writing tools and technologies. Here are a few highlights that you, our community, have shared with us:
Don Watkins is an educator, entrepreneur, open source advocate, life long learner, and Python teacher. Don was among the first to share articles with us, writing about open source tools:
Seth Kenlon is a Unix and Linux geek, open source enthusiast, and tabletop gamer. Between gigs in the film industry and the tech industry (not necessarily exclusive of one another) he likes to design games and hack on Java or Lua code (also not necessarily exclusive of one another). Seth shared these excellent articles about tools and skills:
- 5 things you didn't know about styles in your word processor
- Tables and data structure
- Are you using examples correctly in your technical writing?
- Steps of an algorithm
- Grammar for technical writers
- How to write with Docbook
Ben Cotton is the author of Program Management for Open Source Projects and a long-time contributor to the Fedora Project and other open communities. Ben shared several articles with us about clarity in technical writing:
- Stop writing like an engineer
- Footnotes and asides are a warning
- It's better to be clear than correct
- Use your tools, but write like you
- Write for those who read it
- Git for writing documentation
Ashley O’Brien is a design innovator, UX mentor, and mixed methods researcher. We loved reading Ashley's journey to technical writing:
Robin Bland is a technical writer in the Minneapolis/St Paul area. Robin contributed several article series about technical writing tools, including Oxygen XML Editor and Microsoft Word:
- Manage DITA projects in Oxygen XML Editor
- DITA topics with Oxygen XML Editor
- DITA Concept files in Oxygen
- DITA Task files in Oxygen
- Just the facts: DITA References in Oxygen
- Putting it all together with DITA Maps
- Styles in Microsoft Word
- Paragraph spacing in Microsoft Word
- Page headers and footers in Word
- Images in Microsoft Word
- Multi-column layout in Word
- Adding a full-width byline in Word
Shareen Mann has been writing and editing in a variety of fields for over 25 years. Shareen shared several articles about accessibility and universal design:
Peter Schaffter is the author and maintainer of the "mom" macros for GNU groff. Thank you to Peter for this excellent article about how to write your first document with the groff "mom" macros:
Walter Alejandro Iglesias also contributed an excellent article about using GNU groff. Walter explained how to use different fonts in groff documents:
Martin Anderson-Clutz is a Senior Solutions Engineer at Acquia. Martin wrote a pair of insightful articles about how to use AI in web content:
Nadiia Nykolaichuk, also known as Nadine, is a technical copywriter at ImageX who started her journey with Drupal in 2015. Nadiia shared a ton of great articles about how to get the most out of Drupal:
- What's new and cool in Drupal 10.1
- ChatGPT Integration with Drupal websites
- Using ChatGPT content assistance with Drupal
- How To Schedule Content For Future Publishing In Drupal
- Boost SEO with URL Redirects in Drupal
- Why and How to Add a Live Chat to Drupal
- Image Lazy-loading in Drupal
- Content Editing Experiences with CKEditor 5 in Drupal
- Managing Menus in Drupal 10
- Crafting a FAQ page on a Drupal website
- Configuring roles and permissions in Drupal
Thanks for sharing your advice
We also love hearing from our community about working in their field. You share your advice and experience with us, and we love the discussion. Thanks for these insightful interviews about technical communication:
Brian Kernighan is well known for his work in computing and the many books he has written about working with technology. Brian talked with us about the history of nroff and troff, and how technical writers can explore these tools today.
Seth Kenlon discussed working in technical writing and his approach to writing.
AmyJune Hineline shared her journey in technical writing.
Don Watkins discussed his experience as a technical writer about Linux and open source software.
Mike Saunders answered our questions about LibreOffice, its history, and what it can do.
Nick Rosencrans discussed usability testing, how to do usability testing, and how to get started in the field.
Jerry Saltzer is known for many things in computer science, including Kerberos and Project Athena. We asked him about his work on RUNOFF, an early text processing system.
G. Branden Robinson discussed the history and latest developments in GNU groff.
Deri James shared insights about working on the groff system, including the gropdf
processor.
Eric Allman created many of the components that drive modern computing, such as sendmail and syslog. We asked Eric about creating the troff -me macro package to prepare technical papers.
Radu Coravu shared his insights in how technical writers can leverage DITA, and about using Oxygen XML Editor.
Marshall Kirk McKusick is well known for his extensive work with BSD Unix and Usenix. Kirk is also a prolific author on operating systems; we asked him about how he uses groff to write his books.
Ron McFarland discussed how technical writers can communicate effectively across cultures and languages.
Joe Emery shared his experience in copywriting and the role of the copywriter.
Nate Birt discussed writing his new book, including his writing process and tools.
Thanks to everyone
Technically We Write is surrounded by a wonderful community of writers and readers. We love that you are joining us every day to learn about technical communication skills, tools, and technologies.
We welcome everyone to write with us. We want to hear from you! Contact us to write a how-to article, share an interview, or tell your technical writing story. Our editor is jim@hallmentum.com