Series · The web as a system capability
The web as a system capability: a chronological reference
This reference serves the "web as a system capability" series. It does not try to define an inevitable history of technical progress. It records what each turning point changed: how content gets published, how a request triggers computation, who carries the running cost, and how independent sites respond to each other.
| When | Point | Why it matters to this series | Primary source |
|---|---|---|---|
| 1989 | Tim Berners-Lee proposes the World Wide Web at CERN | The web starts as a cross-organisation information sharing proposal, not an application platform in today's sense. | W3C history |
| 1990 | First browser/editor and server implementations | The early web imagined reading and authoring at the same time. | W3C WorldWideWeb |
| 1991–1993 | The web opens outward; CERN releases the implementation and protocol on royalty-free terms | Linked documents, browsers, cross-platform software and open terms together drove adoption. | CERN |
| Early 1990s | Gopher is a significant way to navigate information | The web's spread was not one format winning alone; publishing and navigation experience were also competing. | University of Minnesota |
| 1993 onward | CGI becomes the common interface for web servers to invoke programs | A URL no longer only returns a pre-existing file; the web gains programmatic responses. | RFC 3875 |
| 1994 | PHP begins as a CGI-form tool | Templates, HTML and data access gradually enter one site implementation. | PHP history |
| 1996 | Microsoft ships FrontPage | Visual site building for non-programmers, lowering the authoring and maintenance barrier before the blog wave. | Microsoft press release |
| 1997 | Jørn Barger uses the term "weblog" | Continuous updating, linking and personal records become a recognisable publishing form. | Wired retrospective |
| Late 1990s to early 2000s | Java Servlets, JSP and J2EE-style server web applications become a major route | The web can be handled by application servers, databases and transactional business logic together. This does not mean every site used Java, but the application stack became one of the mainstream ways to organise work. | Oracle: Java Servlet technology |
| 1999 | Blogger launches and the word blog spreads | Repeated posting, templates, archives and hosting are folded into a lighter workflow. | Blogger history |
| 2000 | Apple HomePage ships as an iTools service | Templates, drag and drop and photo publishing let consumers create a personal page without writing code. | Apple |
| 2002 | TrackBack ships as a Movable Type feature and open specification | A cross-site response can stay on the responder's own site and notify the original. | Movable Type |
| 2002 | .Mac combines iDisk, personal pages and photo publishing into a hosted service | Local authoring and hosted publishing are combined as a product. | Apple |
| 2004–2005 | Ruby on Rails and Django appear | Convention-driven, batteries-included frameworks fold routing, ORM, migrations, templates and scaffolding into a more coherent development experience. They did not invent MVC, databases or all of modern web practice. | Rails releases; Django's first release |
| 2005 | "Ajax" is named as a class of frontend interaction pattern | The browser gradually becomes a stronger application runtime. | Jesse James Garrett |
| 2006 | Apple ships iWeb | Desktop software, templates and one-click publishing lower the barrier to personal sites and media publishing. | Apple |
| 2008 | GitHub Pages announces publishing by Git push | Version control and static publishing form a new simplified path. | GitHub |
| 2011 | Amazon S3 adds static website capability | Object storage can carry part of the public web's publishing job directly. | AWS |
| 2012 | Google Drive Site Publishing launches | An ordinary folder can briefly become a static web publishing space. | Google developers blog |
| 2013 | React is open sourced | Component-based client UI becomes one of the modern web's major routes. | React version history |
| 2015 | Netlify launches Git-driven deployment | Git-driven builds and publishing get productised. It was not the first static hosting or Git-push publishing; the related capabilities in GitHub Pages and S3 came earlier. | Netlify's decade retrospective |
| 2015–2016 | Google Drive Web Hosting is deprecated and shut down | File sharing and website hosting separate again; Google recommends dedicated hosting services. | |
| 2016 | Netlify introduces Deploy Previews | Every pull request gets its own preview URL, and the deployment workflow starts binding building, review and going live more tightly. | Netlify: Deploy Previews |
| 2016 | ZEIT's now starts from simplifying application deployment | now tried to fold deployment, SSL and routing into a shorter path. It and Netlify are not a linear story of one replacing the other. | ZEIT is now Vercel |
| 2016–2017 | Dropbox phases out HTML rendering and public sharing in the Public folder | The cloud drive's lightweight static publishing capability exits, and ordinary share links separate from site publishing again. | Dropbox |
| 2017 | Webmention becomes a W3C Recommendation | Verified cross-site link notification becomes an open standard. | W3C Webmention history |
| 2018 | ActivityPub becomes a W3C Recommendation | Actors, inbox/outbox and activity delivery give federated social systems a standard model. | W3C ActivityPub |
| 2020 | ZEIT becomes Vercel | The Git to preview to shipping workflow continues to cover static delivery, and also common server rendering, function/API routes and edge runtime work. It does not carry every backend or full-stack need for a team. | Vercel rename note; Vercel Git deployments; Vercel Functions |
| 2020 | ArcBlock releases ABT Node 1.0 | Another route to reducing deployment and operational friction: a runtime you deploy and manage yourself, able to install, compose, run and manage static or dynamic blocklets, with routing, DID/identity, authorization and lifecycle. It is not a direct substitute for Netlify or Vercel, nor something to rank against them. | ArcBlock: ABT Node 1.0 |
| Late 2021 | ABT Node is renamed Blocklet Server | The rename does not invert the history: the system released in 2020 was called ABT Node, and continued later as Blocklet Server. | ArcBlock: Blocklet Server 1.6.0 |
| 2023 | v0 brings prompt-to-UI into the development flow | The initial focus was generating React, Tailwind CSS and shadcn/ui code from prompts, later connecting to Vercel's deployment path. Natural language moved the entry point earlier without removing the boundaries of deployment, data, identity or runtime. | Vercel: Announcing v0; v0 deployment notes |
| 2024–2025 | Lovable organises prompt building, preview and explicit publishing into one workflow | A project can produce a shareable preview, and publishing is a separate act that yields a lovable.app URL or a custom domain. It lowers the barrier to entry without turning production publishing into the automatic result of one sentence. | Lovable: Publish; Lovable: Share project |
| ARC's current stage | The Web Device, UI Device, AFS and generic comment/reaction primitives evolve together | What ARC works on is a different recurring layer of system capability: the responsibility boundaries between data, identity, permissions, publishing, interaction and runtime, rather than providing another web framework or hosting service. | ArcBlock: Web Device; this series re-checks implementation boundaries against the current version before publishing |
What to watch for when reading this timeline
public_htmlis Apache's UserDir server convention, and should not be treated as the same product as the macOSSitesdirectory or Apple's HomePage/iWeb.- Weblog, blogging tools and TrackBack correspond to a writing form, a publishing workflow and a cross-site response notification. They are related, and they are not one invention.
- Dropbox Public folder, Google Drive Web Hosting, Google Sites and Google Cloud Storage are different products or capabilities. Do not infer the past hosting capability from today's file sharing features.
- GitHub Pages, S3, Netlify, ZEIT/now, Vercel, v0 and Lovable sit at different positions across static hosting, deployment workflow and prompt-driven building. Lining them up as one chain of replacements loses the problem each of them solved.
- ABT Node was the name at the 2020 release and Blocklet Server is the later name. They should not be written up as two independent products each starting from nothing.
- Webmention and ActivityPub are not protocols at the same layer either. The first is verified link notification; the second defines a federated activity model.
- ARC's outward interoperability with Webmention and ActivityPub is still a design goal, not an existing compatibility feature.