Here is a list of some pages, samples, or projects I’ve worked on.

Game engine

  1. Unity UI Toolkit: In 2021 I helped plan, reorganize, and write content for a product that had a significant documentation backlog. I’m proud of the work I did to help make this product a success.
  2. Unity SystemGraph: Another great project. I helped organize and structure the SystemGraph documentation to make it more accessible to systems engineers.
  3. Unity SensorSDK: A personal favorite. One of the best engineering teams I’ve ever worked with. I’m especially proud of the Get Started section, which was well received by our customers.

Aerospace & civil aviation

Unfortunately all of my aviation documentation is behind the veil of strict non-disclosure agreements (NDA). But I can provide links to the type of work you would expect. Aviation writing usually follows three core rules:

  1. Word usage is limited and follows ASD-STE100 standards.
  2. All changes must be tracked, no matter how small.
  3. All work must follow a strict schema or information architecture.

Specifications

The following are some examples of specifications I’ve used during my time in the aviation industry:

  • The ASD-STE100 defines all writing specifications for most technical documentation in the aviation and aerospace industries.
  • S1000D Another specification for technical publications. In use for mostly maintenance manuals and items that might have multiple variants to allow for modular content when producing publications. Uses “data modules”, which might bring happiness or despair to the face of a technical writer, depending on their experience with the specification.
  • iSpec2200: Also known as the ATA Standard Numbering System. These manuals outline the requirements and structure for producing documentation for an Aircraft Flight Manual (AFM) or an Aircraft Maintenance Manual (AMM).

Examples

Here are some examples of aviation technical manuals that aren’t behind a non-disclosure agreement: