openskills.info
← Technical Writer career guide

Product and design

Technical Writer timeline

How the field of a Technical Writer got here: the sourced milestones from every published course of this career, on one axis.

1976 to 2025

137 milestones across 15 courses

  • Core
  • Supporting
  • Specialization

The axis stretches toward recent years, where most milestones fall. Bars count milestones per year; dots are single milestones.

Before 1990

2 milestones

  1. 1976

    Information Architect named at the AIA conference

    Richard Saul Wurman used Information Architect in connection with the Architecture of Information conference. His usage centered on making information understandable.

  2. 1987

    Word 4.0 ships revision marks

    Microsoft Word 4.0 introduces revision marks, letting an author see where a document changed and a reviewer react to edits in place — an early form of diff-aware document review inside a word processor.

1990s

12 milestones

  1. 1991

    Graphviz initial public release

    Bell Labs researchers release Graphviz, an open-source graph visualization package that renders DOT language descriptions into diagrams. It establishes the idea that graphs can be defined in text and rendered automatically, predating the diagram-as-code movement by over a decade.

  2. 1994

    Argus Associates began web information architecture work

    Argus brought library and information-science methods to early Internet and web projects. Its practitioners used architecture to emphasize structure and organization in digital information environments.

  3. 1997

    UML 1.0 adopted by OMG

    The Object Management Group adopts the Unified Modeling Language 1.0, standardizing notation for class, sequence, use case, and activity diagrams. UML gives software teams a shared vocabulary for structural and behavioral modeling that persists through subsequent revisions.

  4. 1998 Feb

    The first Polar Bear book edition published

    O'Reilly published Information Architecture for the World Wide Web by Louis Rosenfeld and Peter Morville. The book organized web IA around systems for finding and understanding information.

  5. 1999 May 5

    WCAG 1.0 becomes a W3C Recommendation

    WCAG 1.0 made accessibility guidance a stable web standard with checkpoints for content providers. Technical content design gained an explicit requirement to make information available beyond a single visual presentation.

2000s

29 milestones

  1. 2000 Apr

    The first Information Architecture Summit convened

    ASIS organized the first summit after recognizing overlap between practical web IA and information-science research. The event established a recurring professional gathering for the field.

  2. 2001

    ISO 15489 first published

    ISO published its first international records-management standard. It established a common framework for policies, responsibilities, systems, and recordkeeping practices that ECM designs can apply to business content.

  3. 2001 Feb

    Agile Manifesto published

    The Agile Manifesto placed people and collaboration alongside working software as software-delivery values. It established a widely used foundation for treating team conditions as part of delivery practice.

  4. 2001 Mar 15

    WSDL 1.1 published as a W3C Note

    WSDL 1.1 was published as a W3C Note. It provided an XML description of a web service’s operations, messages, and bindings.

  5. 2002 Nov

    AIfIA launched

    The Asilomar Institute for Information Architecture launched as a professional organization. Its mission focused on advancing the design of shared information environments and connecting the global community.

  6. 2004 Dec

    Markdown 1.0.1 is released

    Markdown made readable plain-text source a practical input to HTML publishing. Its source-and-output split became a common building block for documentation repositories.

  7. 2005

    DITA 1.0 ratified as an OASIS Standard

    OASIS members approve DITA version 1.0, giving topic-based, single-sourced XML authoring a formal open standard for enterprise adoption.

  8. 2005

    Git becomes available

    Git introduced a distributed version-control model that made branches, commits, and diffs routine evidence for source changes. Documentation could use the same history and review mechanics as software.

  9. 2005 May 31

    DITA 1.0 becomes an OASIS Standard

    DITA standardized an XML architecture for topic-oriented information. It made information types and reusable modules part of a formal publishing model for technical content.

  10. 2005 Jun

    DITA 1.0 becomes an OASIS Standard

    DITA established a topic-oriented XML architecture for designing, managing, and publishing information for print and the web.

  11. 2006

    Google Docs launches

    Google launches Docs as a browser-based word processor, bringing simultaneous editing to documents and later threaded comments — the real-time collaboration model that many review workflows use today.

  12. 2006

    ISO 23081 metadata principles published

    ISO 23081-1 set out principles for records-management metadata. It made metadata a formal concern for creating, managing, and using records rather than a repository convenience.

  13. 2007

    PlantUML first released

    PlantUML publishes its initial version, offering a text-to-UML rendering pipeline. It makes UML diagram generation accessible from plain text, establishing a pattern that later tools like Mermaid would follow with simpler syntax.

  14. 2007 Jun 26

    WSDL 2.0 became a W3C Recommendation

    WSDL 2.0 became a W3C Recommendation. It separated an abstract service description from the concrete details of how and where the service is offered.

  15. 2007 Aug 13

    DITA 1.1 becomes an OASIS Standard

    DITA 1.1 added structures including bookmaps, glossaries, and richer metadata. Those additions expanded the formal relationships available between technical content units.

  16. 2008

    Lucidchart launches

    Lucidchart launches as a browser-based collaborative diagramming tool, making real-time co-authoring of diagrams accessible without desktop software. It demonstrates that the web can support professional-grade diagramming workflows.

  17. 2008

    Pull requests bring review to version control

    GitHub introduces the pull request, turning a proposed change into a first-class unit that others can comment on before it merges. The pull request becomes the standard container for documentation review in version-controlled projects.

  18. 2008 Mar

    Sphinx 0.1 is released

    Sphinx introduced a documentation generator that made structured source files and generated output a practical workflow for software projects.

  19. 2008 Mar

    Sphinx 0.1 reaches its first public release

    Sphinx published HTML and LaTeX builders from documentation source and tracked dependencies between inputs. It demonstrated a repeatable documentation build rather than manual output editing.

  20. 2008 Mar

    Sphinx released for Python's documentation

    Georg Brandl releases Sphinx to replace Python's LaTeX-based documentation, introducing reStructuredText-based builders that produce HTML, PDF, and man pages from one source tree.

  21. 2008 Dec 11

    WCAG 2.0 becomes a W3C Recommendation

    WCAG 2.0 reframed accessibility requirements for broader technology use and more testable conformance. Content structure and interaction could be evaluated against a stable, technology-neutral standard.

  22. 2009

    First devopsdays held in Ghent

    The first devopsdays brought together software-development and operations communities. The event series made cross-functional delivery and operations a shared professional conversation.

  23. 2009 Oct

    DocBook V5.0 becomes an OASIS Standard

    DocBook V5.0 became an OASIS Standard as an XML vocabulary, continuing the structured-authoring path for technical content.

2010s

71 milestones

  1. 2010

    CMIS 1.0 became an OASIS standard

    Content Management Interoperability Services version 1.0 was approved as an OASIS standard. It defined a common interface for generic content-management capabilities across repositories.

  2. 2010

    ISO 16175 parts 1–3 published

    ISO published the first ISO 16175 suite for digital records. It supplied guidance on functional requirements for systems that create and manage digital records.

  3. 2010

    Read the Docs founded

    Eric Holscher, Charlie Leifer, and Bobby Grace launch Read the Docs from a hackathon, giving Sphinx projects free automated builds and hosted, versioned documentation.

  4. 2010 Dec 1

    DITA 1.2 becomes an OASIS Standard

    DITA 1.2 separated technical-content and learning-and-training specializations within the specification. Authors could model different information purposes with a more explicit structured-content vocabulary.

  5. 2011

    ISO/IEC/IEEE 26511 standardizes documentation management

    ISO/IEC/IEEE 26511:2011 defines requirements for managers of user documentation, formalizing the lifecycle in which a change is reviewed before it is released.

  6. 2011

    Semantic Versioning 1.0.0 published

    Tom Preston-Werner's SemVer 1.0.0 gave MAJOR.MINOR.PATCH a precise compatibility meaning that later changelog practice could hang on.

  7. 2011 Aug 10

    Swagger Specification 1.0 released

    The first Swagger Specification release established a formal document format for describing APIs. Documentation tools could consume that description instead of relying only on manually maintained endpoint pages.

  8. 2012

    Developer Experience concept and definition published

    Fagerholm and Münch described developer experience as developers thoughts and feelings about work in their project environment. The publication made the human experience of development an explicit software-engineering topic.

  9. 2012

    Read the Docs adds GitHub webhook builds

    Repository events could trigger documentation builds without a separate manual publishing step. This moved the documentation deployment path closer to normal change integration.

  10. 2013

    CMIS 1.1 added browser binding support

    OASIS approved CMIS 1.1, including a browser JSON binding. The standard continued to position interoperability as a layer over existing content-management systems rather than a replacement for their full capabilities.

  11. 2013

    First State of DevOps Report published

    Puppet published the first annual State of DevOps Report, starting the survey research program that later evidence-based audit frameworks trace back to.

  12. 2013

    Write the Docs brings review into the open

    The first Write the Docs conference gathers documentation practitioners, spreading the practice of treating documentation as code — versioned, reviewed, and deployed through the same workflow as software.

  13. 2013 Jun 18

    Semantic Versioning 2.0.0 released

    SemVer 2.0.0 refined precedence, pre-release, and build metadata rules that tooling and changelog preambles still reference.

  14. 2014

    Mermaid.js first published

    Knut Sveidqvist publishes Mermaid, a JavaScript library that generates diagrams from Markdown-like text syntax. Its integration into GitHub's Markdown renderer makes diagram-as-code practical in pull requests and documentation without any external tooling.

  15. 2014

    MkDocs 0.8 is released

    MkDocs offered a Markdown-and-configuration path to a static documentation site. It gave teams a lightweight generator for local previews and automated builds.

  16. 2014

    State of DevOps Report connects culture and delivery performance

    The 2014 report presented DevOps as a cultural as well as technical shift and reported links between its practices and IT performance. It made developer and organizational conditions part of delivery improvement work.

  17. 2014

    State of DevOps Report links job satisfaction to performance

    The 2014 report found job satisfaction to be a leading predictor of organizational performance and connected practices such as continuous delivery to measurable IT performance.

  18. 2014 Jan

    conventional-changelog published on npm

    Early automation began turning structured commit histories into changelog drafts years before Conventional Commits reached 1.0.0.

  19. 2014 Sep 8

    Swagger 2.0 formal document released

    Swagger 2.0 released a new formal description document. Its versioned structure gave documentation publishers a defined input for generated reference material.

  20. 2015

    DORA formed as an independent research program

    Nicole Forsgren, Jez Humble, and Gene Kim formed DevOps Research and Assessment (DORA) to continue the State of DevOps research as a dedicated organization.

  21. 2015

    GitLab adds merge request approvals

    GitLab Enterprise Edition introduces merge request approvals, letting projects require a named set of approvers before an MR can merge — an early example of review verdicts enforced by the tool.

  22. 2015 Sep

    The fourth Polar Bear edition expanded beyond the web

    Information Architecture for the Web and Beyond added cross-channel design, mobile, meaning-making, system design, and context. The title change reflected architecture across connected information environments.

  23. 2015 Sep 3

    GitHub adds protected branches and required status checks

    GitHub launches protected branches and required status checks, so a repository can block merges until the configured reviews and automated checks pass. The merge gate becomes a platform feature, not a team convention.

  24. 2015 Nov

    OpenAPI Initiative formed

    SmartBear donates the Swagger specification to the Linux Foundation, forming the OpenAPI Initiative and starting the transition from a vendor format to a community-governed standard.

  25. 2015 Dec

    Swagger becomes the OpenAPI Specification

    The OpenAPI Initiative took stewardship of a vendor-neutral API description format, strengthening documentation that both people and tools can use.

  26. 2015 Dec 17

    DITA 1.3 becomes an OASIS Standard

    DITA 1.3 continued the standard's topic and map architecture while adding standardization for more specialized content needs. Structured authoring could retain common relationships while extending the model for a domain.

  27. 2015 Dec 31

    Swagger 2.0 donated to the OpenAPI Initiative

    SmartBear donated Swagger 2.0 to the OpenAPI Initiative, where it became the OpenAPI Specification. The format moved to neutral, collaborative governance for tool builders and API providers.

  28. 2016 Apr

    ISO 15489-1 second edition published

    ISO released the revised records-management concepts and principles standard. The revision addressed records across changing digital and collaborative environments while retaining technology-neutral guidance.

  29. 2016 Jul 11

    OpenAPI Initiative described the specification governance process

    The OpenAPI Initiative published its process for evolving the formerly Swagger specification. The process enabled competing vendors to collaborate on the same API-description standard.

  30. 2016 Sep 14

    GitHub Reviews formalizes review states

    GitHub announces pull request Reviews at its Universe event: a reviewer can formally approve or request changes on a pull request, and admins can require reviews before merge. The comment, approve, and request-changes states this course teaches come from here.

  31. 2017

    Docusaurus 1.0 released

    Facebook releases Docusaurus after years of copy-pasting a Jekyll template across internal projects, shipping MDX, versioning, and internationalization built in.

  32. 2017 Feb 14

    Vale 0.1.0 releases

    The first release of Vale, a natural-language linter for prose, makes style enforcement automatable on documentation changes. Vale is an example of the style checks this course's review loop runs before a human reads the diff.

  33. 2017 Jul

    OpenAPI 3.0 released

    The OpenAPI Initiative ships specification version 3.0.0, adding a centralized component model and multi-server support that API-reference renderers such as Swagger UI and Redoc build on.

  34. 2017 Jul 6

    CODEOWNERS routes reviews to the right people

    GitHub introduces CODEOWNERS, so a repository can name the people responsible for each path and a change in that area automatically requests their review. Code ownership gives the review loop a routing rule instead of a mailing list.

  35. 2017 Jul 26

    OpenAPI Specification 3.0 released

    OpenAPI Specification 3.0 was released. Documentation tooling could begin supporting the 3.0 document structure as a distinct specification version.

  36. 2017 Oct

    Docusaurus 1.0.0 is released

    Docusaurus established another documentation-site generator that keeps pages and navigation in repository source. Teams could integrate a documentation build into a JavaScript-oriented project workflow.

  37. 2017 Oct

    ISO 23081-1 metadata principles updated

    ISO published an updated metadata-principles edition aligned with ISO 15489:2016. The update reflected experience managing records metadata in digital environments.

  38. 2017 Dec

    Docusaurus is introduced

    Docusaurus packaged versioning, search, navigation, and publishing infrastructure for software documentation websites.

  39. 2018

    C4 Model published by Simon Brown

    Simon Brown publishes the C4 model, a framework for software architecture diagrams organized as four zoom levels: context, container, component, and code. It provides the progressive-disclosure discipline that this course teaches as the primary approach to choosing view types.

  40. 2018 Mar

    Accelerate book formalizes the four keys

    "Accelerate: The Science of Lean Software and DevOps" consolidated four years of research into deployment frequency, lead time, change failure rate, and recovery time as the core software delivery performance metrics.

  41. 2018 Jun 5

    WCAG 2.1 becomes a W3C Recommendation

    WCAG 2.1 added guidance for mobile, low-vision, and cognitive and learning needs. Content and interface design had to account for more ways readers perceive and operate a documentation site.

  42. 2018 Dec

    Google acquires DORA

    Google Cloud acquired DORA, folding its research program into Google Cloud and giving the four keys a permanently funded research home.

  43. 2019 Apr

    Release Please repository created

    Google's Release Please project automated Conventional Commits–based changelog and version pull requests for multi-language repos.

  44. 2019 Sep

    World IA Day became independent

    The IA Institute voted to dissolve, and World IA Day formed a separate nonprofit organization. Community activity continued under a new governing body.

2020s

23 milestones

  1. 2020

    Diátaxis is publicly introduced

    Diátaxis gave teams a named framework for separating tutorials, how-to guides, reference, and explanation. It reinforced that a successful documentation pipeline still needs deliberate information architecture.

  2. 2020

    ISO 16175 functional requirements consolidated

    ISO 16175-1:2020 provided functional requirements and associated guidance for applications that manage digital records. It consolidated earlier ISO 16175 material for system selection, design, implementation, and maintenance.

  3. 2020

    Structurizr DSL released

    Structurizr publishes a domain-specific language for defining C4 model diagrams as code. It ties architecture documentation to a text source that can be versioned, reviewed, and rendered into the four C4 view types automatically.

  4. 2020 Mar

    Spotify open-sources Backstage

    Spotify released its internal developer portal, Backstage, as open source, giving audit teams a reusable software catalog for tracking ownership and standards across services.

  5. 2020 Mar

    Spotify releases Backstage as open source

    Spotify released Backstage as a platform for developer portals that unifies tooling, services, and documentation. The release gave platform teams a reusable implementation route for software catalogs and developer portals.

  6. 2020 Aug

    Backstage Software Templates announced

    Backstage introduced templates for creating software components with organization-specific standards built in. The feature connected portal discovery to repeatable self-service paths for new work.

  7. 2020 Sep

    Backstage accepted into the CNCF Sandbox

    The Cloud Native Computing Foundation accepted Backstage into its Sandbox, beginning vendor-neutral governance of the developer-portal category that audit-driven scorecards now build on.

  8. 2021 Feb

    SPACE framework published

    The SPACE framework described developer productivity as five dimensions rather than a single activity measure. It provided a measurement guardrail for DevEx work that combines satisfaction, collaboration, and flow with performance and activity.

  9. 2021 Feb

    The SPACE framework is published

    Researchers from Microsoft, GitHub, and the University of Victoria published the SPACE framework in ACM Queue, defining five dimensions of developer productivity to prevent single-metric claims.

  10. 2021 Feb 15

    OpenAPI Specification 3.1 released

    OpenAPI Specification 3.1 was released with updated JSON Schema support. API reference generators and validators needed to account for the 3.1 schema vocabulary and reference behavior.

  11. 2022

    D2 scripting language released

    Terrastruct releases D2, a modern diagram scripting language with improved auto-layout and a focus on developer ergonomics. It advances the diagram-as-code category by treating layout as a first-class concern rather than an afterthought.

  12. 2022 Mar

    Backstage 1.0 and CNCF incubation announced

    Backstage 1.0 marked the project transition out of beta while its CNCF incubation signaled broader technical governance. The milestone reflected the maturation of an open-source option for developer-portal practice.

  13. 2022 Mar

    Backstage reaches CNCF Incubating status

    Backstage moved from the CNCF Sandbox to Incubating maturity, reflecting wider adoption of catalog-driven developer portals as an operational layer for engineering standards.

  14. 2023

    DevEx: What Actually Drives Productivity is published

    Noda, Storey, Forsgren, and Greiler published the DevEx framework in ACM Queue, condensing developer experience into three measurable dimensions — feedback loops, cognitive load, and flow state.

  15. 2023

    Excalidraw acquires tldraw

    Excalidraw, the freehand collaborative sketching tool, acquires tldraw. The merger consolidates the low-fidelity sketching category and validates freehand diagramming as a distinct phase in the diagramming workflow, complementary to formal diagram-as-code tools.

  16. 2023

    Mermaid enters GitHub Markdown natively

    GitHub adds native rendering support for Mermaid diagrams in Markdown files. Diagram-as-code diagrams in pull requests, issues, and documentation can now be rendered by the platform itself, removing the need for external rendering plugins.

  17. 2023 Oct 5

    WCAG 2.2 becomes a W3C Recommendation

    WCAG 2.2 added success criteria for focus visibility, dragging, target size, consistent help, and authentication. Information design for technical content continued to include navigation and task-completion behavior, not only prose.

  18. 2024

    DX Core 4 introduced

    Laura Tacho and Abi Noda introduced the DX Core 4 framework, combining DORA, SPACE, and DevEx into four balanced outcomes with the Developer Experience Index as the self-reported effectiveness measure.

  19. 2024 Oct 24

    OpenAPI 3.1.1

    The release identified published HTML specifications as authoritative source text for resolving interpretation questions.