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.
Product and design
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
The axis stretches toward recent years, where most milestones fall. Bars count milestones per year; dots are single milestones.
2 milestones
1976
Richard Saul Wurman used Information Architect in connection with the Architecture of Information conference. His usage centered on making information understandable.
1987
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.
12 milestones
1991
HaL and O'Reilly develop a document vocabulary for exchanging UNIX documentation.
1991
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.
1994
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.
1995
Microsoft begins providing writing guidelines that later evolve into the Microsoft Manual of Style and the web Writing Style Guide.
1996
Wurman's book presented work by people shaping complex information into understandable forms. It also made his earlier use of the Information Architect label visible to web practitioners.
1997
DocBook V3.0 provided a widely adopted structured vocabulary for technical books and software documentation.
1997
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.
1997 Mar
BCP 14 defines MUST, SHOULD, MAY and related key words for requirement levels in IETF documents, creating a portable terminology for normative force.
1997 Oct
Dimitri van Heesch releases Doxygen 0.1, establishing the pattern of generating reference documentation directly from source-code comments.
1998 Feb
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.
1998 Jul
Responsibility for maintaining the DocBook DTD moved to the OASIS DocBook Technical Committee.
1999 May 5
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.
29 milestones
2000 Apr
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.
2001
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.
2001 Feb
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.
2001 Feb
DocBook XML 4.1.2 receives OASIS specification status alongside the SGML vocabulary.
2001 Mar 15
WSDL 1.1 was published as a W3C Note. It provided an XML description of a web service’s operations, messages, and bindings.
2002 Nov
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.
2004 Dec
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.
2005
OASIS members approve DITA version 1.0, giving topic-based, single-sourced XML authoring a formal open standard for enterprise adoption.
2005
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.
2005 May 31
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.
2005 Jun
OASIS announces approval of a topic-oriented architecture for reusable technical content.
2005 Jun
DITA established a topic-oriented XML architecture for designing, managing, and publishing information for print and the web.
2006
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.
2006
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.
2007
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.
2007 May
DITA 1.1 extended the standard while remaining compatible with DITA 1.0, reinforcing reusable structured content.
2007 Jun 26
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.
2007 Aug 1
The next standardized architecture becomes a reference point for compatible authoring and processing.
2007 Aug 13
DITA 1.1 added structures including bookmaps, glossaries, and richer metadata. Those additions expanded the formal relationships available between technical content units.
2008
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.
2008
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.
2008 Mar
Sphinx introduced a documentation generator that made structured source files and generated output a practical workflow for software projects.
2008 Mar
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.
2008 Mar
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.
2008 Nov
Tom Preston-Werner releases Jekyll, a Ruby static site generator that becomes GitHub Pages' native build engine.
2008 Dec 11
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.
2009
The first devopsdays brought together software-development and operations communities. The event series made cross-functional delivery and operations a shared professional conversation.
2009 Oct
DocBook V5.0 became an OASIS Standard as an XML vocabulary, continuing the structured-authoring path for technical content.
2009 Nov 1
The XML vocabulary adopts RELAX NG and Schematron as its normative validation model.
71 milestones
2010
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.
2010
ISO published the first ISO 16175 suite for digital records. It supplied guidance on functional requirements for systems that create and manage digital records.
2010
Read the Docs connected version-controlled documentation projects to hosted builds and published versions. The hosting model made a buildable documentation repository accessible to more projects.
2010
Eric Holscher, Charlie Leifer, and Bobby Grace launch Read the Docs from a hackathon, giving Sphinx projects free automated builds and hosted, versioned documentation.
2010 Dec
The expanded architecture includes key-based addressing for publication-context indirection.
2010 Dec 1
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.
2011
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.
2011
Tom Preston-Werner's SemVer 1.0.0 gave MAJOR.MINOR.PATCH a precise compatibility meaning that later changelog practice could hang on.
2011 Aug 10
The first Swagger Specification release established the lineage of the later OpenAPI format.
2011 Aug 10
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.
2012
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.
2012
The 2012 Manual of Style becomes the cited predecessor for the later public Microsoft Writing Style Guide refresh.
2012
Repository events could trigger documentation builds without a separate manual publishing step. This moved the documentation deployment path closer to normal change integration.
2012 Feb 11
The IA Institute hosted a one-day event across 14 cities under the theme Designing Structures for Understanding. The event created a distributed format for practice and education.
2012 Aug 22
A new published specification version advanced the early interface description format.
2013
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.
2013
Puppet published the first annual State of DevOps Report, starting the survey research program that later evidence-based audit frameworks trace back to.
2013
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.
2013 May
Jekyll reaches its 1.0 release, stabilizing the tool GitHub Pages had standardized on as its default build engine.
2013 Jun 18
SemVer 2.0.0 refined precedence, pre-release, and build metadata rules that tooling and changelog preambles still reference.
2014
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.
2014
MkDocs offered a Markdown-and-configuration path to a static documentation site. It gave teams a lightweight generator for local previews and automated builds.
2014
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.
2014
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.
2014 Jan
Early automation began turning structured commit histories into changelog drafts years before Conventional Commits reached 1.0.0.
2014 Jan
Tom Christie releases MkDocs, offering a single-YAML-file alternative to Sphinx's configuration for teams that want Markdown without reStructuredText.
2014 May
Olivier Lacan started collecting human-readable changelog practices that later became the Keep a Changelog convention.
2014 Jun
Google Docs introduces Suggesting mode, where edits appear as proposed changes the author accepts or rejects one by one — a lighter-weight review loop than tracking every edit by hand.
2014 Sep 8
Swagger 2.0 released a new formal description document. Its versioned structure gave documentation publishers a defined input for generated reference material.
2014 Sep 8
The 2.0 release became the version later donated to the OpenAPI Initiative.
2015
Nicole Forsgren, Jez Humble, and Gene Kim formed DevOps Research and Assessment (DORA) to continue the State of DevOps research as a dedicated organization.
2015
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.
2015 Sep
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.
2015 Sep 3
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.
2015 Nov
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.
2015 Dec
DITA 1.3 became an OASIS Standard after additions in earlier releases expanded document and specialization options.
2015 Dec
The OpenAPI Initiative took stewardship of a vendor-neutral API description format, strengthening documentation that both people and tools can use.
2015 Dec 17
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.
2015 Dec 17
The architecture includes key scopes and branch filtering for more specific publication contexts.
2015 Dec 31
The Swagger 2.0 specification was donated to the OpenAPI Initiative.
2015 Dec 31
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.
2016
Martin Donath releases the Material theme for MkDocs, which becomes the default choice for most new MkDocs documentation sites.
2016 Apr
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.
2016 Jul 11
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.
2016 Sep 14
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.
2016 Nov 22
The vocabulary adds topic-oriented structures alongside its document hierarchy.
2017
Facebook releases Docusaurus after years of copy-pasting a Jekyll template across internal projects, shipping MDX, versioning, and internationalization built in.
2017 Feb 14
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.
2017 May
BCP 14 update states that only uppercase RFC 2119 key words carry special meanings; lowercase forms keep ordinary English sense.
2017 Jun 20
Version 1.0.0 settled the six change types and guiding principles that most Keep a Changelog files still follow.
2017 Jul
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.
2017 Jul 6
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.
2017 Jul 26
The 3.0.0 release established a new OpenAPI major version with a revised description structure.
2017 Jul 26
OpenAPI Specification 3.0 was released. Documentation tooling could begin supporting the 3.0 document structure as a distinct specification version.
2017 Sep 6
Google publishes the editorial guide used for its developer documentation so open-source contributors can follow the same voice, formatting, and word-list practice.
2017 Oct
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.
2017 Oct
ISO published an updated metadata-principles edition aligned with ISO 15489:2016. The update reflected experience managing records metadata in digital environments.
2017 Dec
Docusaurus packaged versioning, search, navigation, and publishing infrastructure for software documentation websites.
2018
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.
2018
Microsoft releases an updated public Writing Style Guide with voice principles, a large word list, and terminology collections for modern IT content.
2018 Mar
"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.
2018 Jun 5
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.
2018 Jun 19
OASIS publishes the specification with approved corrections to its architecture and language reference.
2018 Sep 14
Vale ships as an NLP-powered prose linter that enforces team-configured style and terminology rules rather than a single built-in grammar opinion.
2018 Dec
Google Cloud acquired DORA, folding its research program into Google Cloud and giving the four keys a permanently funded research home.
2019 Feb 15
The 1.1.0 revision refined guidance while keeping the same change-type vocabulary projects had already adopted.
2019 Apr
Google's Release Please project automated Conventional Commits–based changelog and version pull requests for multi-language repos.
2019 Sep
The specification reached 1.0.0, stabilizing feat, fix, and breaking-change markers as inputs to version bumps and generated changelogs.
2019 Sep
The IA Institute voted to dissolve, and World IA Day formed a separate nonprofit organization. Community activity continued under a new governing body.
2019 Nov
Red Hat publishes an open supplementary style guide that overrides or supplements IBM Style for product documentation and includes glossary conventions.
2019 Dec
The DevRelCon London talk argued publicly that commit messages and release notes serve different audiences and should not be recycled wholesale.
23 milestones
2020
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.
2020
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.
2020
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.
2020 Mar
Spotify released its internal developer portal, Backstage, as open source, giving audit teams a reusable software catalog for tracking ownership and standards across services.
2020 Mar
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.
2020 Aug
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.
2020 Sep
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.
2021 Feb
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.
2021 Feb
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.
2021 Feb 15
The 3.1.0 release aligned the Schema Object with JSON Schema Draft 2020-12.
2021 Feb 15
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.
2021 Oct 20
GitHub made automatically generated release notes generally available, summarizing merged pull requests on hosted release pages.
2022
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.
2022 Mar
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.
2022 Mar
Backstage moved from the CNCF Sandbox to Incubating maturity, reflecting wider adoption of catalog-driven developer portals as an operational layer for engineering standards.
2022 Dec 25
git-cliff reached 1.0.0 as a configurable changelog generator for Conventional Commits and custom parsers writing repository-owned CHANGELOG files.
2023
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.
2023
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.
2023
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.
2023 Oct 5
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.
2024
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.
2024 Oct 24
The release identified published HTML specifications as authoritative source text for resolving interpretation questions.
2025 Sep 19
A new minor release added features including streaming media type support and richer tags.