Teaching modern technical writing as a connected practice

Technical writers increasingly work across code, APIs, content strategy, and visual communication. The curriculum needed to connect those disciplines while giving students practical ways to build confidence.

The challenge

Students entered with different levels of technical experience. The learning experience had to make unfamiliar tools approachable while showing how each skill contributes to useful, maintainable documentation.

My role

As an instructor, I taught docs-as-code, coding fundamentals, API documentation, content strategy, and visual communication to technical writing students.

The approach

  • Connected technical concepts to realistic documentation work.
  • Made code and API practices accessible to learners with varied backgrounds.
  • Treated visual communication and content strategy as core technical writing skills.
  • Helped students understand how modern documentation teams work across disciplines.

Teaching lens

Strong technical writers do more than explain systems. They learn how content, code, design, and user needs work together.

Explore Algonquin College

Scaling merchant documentation from one language to ten

Expanding global documentation coverage meant coordinating content readiness, localization operations, platform needs, and quality expectations—not treating translation as a final production step.

The challenge

A large merchant audience needed useful documentation across markets. Speed mattered, but so did creating an approach that teams could operate and maintain after launch.

My role

I led the documentation strategy and cross-functional alignment behind the rollout, connecting content, localization, and delivery decisions into one program.

The approach

  • Defined the scope and readiness criteria for full documentation coverage.
  • Aligned partners around sequencing, ownership, and quality expectations.
  • Designed the rollout as an ongoing content operation rather than a one-time translation project.
  • Balanced launch velocity with sustainable maintenance.

Result

10

languages with full merchant-documentation coverage delivered in under six months.

Explore related public documentation

Building documentation leadership around a global developer platform

Developer documentation at platform scale requires more than producing pages. It needs teams with the right capabilities, strong partnerships with engineering and product, and an information experience that helps developers move.

The challenge

Shopify’s developer ecosystem spans APIs, platform concepts, workflows, and a global developer audience. Documentation needed to evolve alongside the platform while remaining navigable and useful.

My role

I built and led technical writing teams responsible for developer documentation and API guides. My work included hiring, team development, documentation structure, and cross-functional leadership.

The approach

  • Built team capability through intentional hiring and development.
  • Connected writers closely with engineering, product, and developer needs.
  • Improved API guide structure, navigation, and documentation experience.
  • Treated shopify.dev as a product surface with an evolving operating model.

Leadership lens

The durable outcome was a documentation capability: people, partnerships, and systems able to support a complex developer platform over time.

Explore related public documentation

Additional experience

Documentation quality, APIs, analytics, and education

Quality and governance

Led the evaluation and purchase of Acrolinx to improve consistency and governance across content teams.

API documentation

Created and maintained Swagger and OpenAPI reference content, SDK documentation, and public REST API guidance.

Technical writing education

Taught docs-as-code, API documentation, coding fundamentals, content strategy, and visual communication.

Continue the conversation

Want the context behind the outcomes?

I can share more about my approach where confidentiality permits.

Get in Touch