flock

#106 [talk] Technical Writing for Non-Writers
Closed: Talk Scheduled Opened by cwickert.

Closed: Talk Scheduled
Reopen Issue

  1. What’s your proposal?
    You need to write (technical) texts now and then, but are unsure how to structure them, how to phrase your content, or how to best address your readers? This talk shows you how to optimize texts to make them easier to understand (and translate). Get to know universal principles that can be applied to a wide variety of text types - including release notes, bug reports, error messages, or e-mails.

  2. Who in addition to the speaker needs to be in the room for this to succeed?

  3. Fedora contributors interested in writing new or improving existing Fedora documentation.
  4. Any FOSS contributor interested in writing or improving documentation.

  5. (Optionally) Some Fedora community and/or documentation people (bex, jflory7, rkratky, asamalik, …)

  6. Is this a

  7. Talk of 60 minutes

  8. Anything else we need to know?
    Even though this talk is about technical writing, it's not a technical talk as in I won't be talking about particular tools or a specific tool chain. Instead, I will introduce universal principles that can be applied to any technical writing.

  9. Who are you?

  10. Name: Christoph Wickert
  11. FAS ID: cwickert
  12. IRC Nick: cwickert

Metadata Update from @bex:
- Issue tagged with: Talk In Consideration

Metadata Update from @bex:
- Issue untagged with: Talk In Consideration
- Issue tagged with: Talk Accepted

Metadata Update from @bex:
- Issue close_status updated to: Talk Scheduled
- Issue status updated to: Closed (was: Open)
Metadata
None

Talk Accepted

None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.