History of building websites, 7 of 10
In the framework years, a simple page came with heavy machinery
Frameworks like React turned web pages into programs, then Jekyll and the static site makers went back to plain pages built once and handed out from nearby
By Orla Finch ·

Say it is 2014, and Jess, who typed her first page by hand back in 1996, now builds websites for a living. Last time we left Rosa on a builder that keeps the code out of her sight. Jess is one of the people who kept the code, and the code around her pages keeps getting bigger.
Early web pages were files typed by hand and put on a server, the computer that hands pages out. From 1993, a standard called CGI let a server make a page on the spot from what a visitor typed. By the late 1990s, web frameworks had arrived: ready-made kits that bundle the jobs nearly every site repeats, like storing data and filling in templates.
Then the machinery spread. Browsers already ran JavaScript, the language that lets a page change after it loads. At Facebook, Jordan Walke built React. It went onto Facebook's News Feed in 2011, and its code was opened to the public in May 2013. React builds a page out of small parts you can reuse, and redraws only the parts that change.
A site built this way is called a single-page application. It loads once, then rewrites the page in place instead of fetching a new one, so moving around feels like using an app. For a tool you sign in to and work in all day, that can be worth it. For a bakery's opening hours, it is a lot of machinery to carry. Before a visitor reads a word, the browser has to download the framework and some of the site's own code, and some search engines, whose robots did not run JavaScript, had trouble reading such sites.
The people who made the machines saw the cost. Next.js, made by the company Vercel and first released in 2016, builds React pages on the server before they are sent. A visitor with JavaScript turned off, or a search engine, gets a finished page, and the wait is shorter.
Some had gone that way already. In 2008 Tom Preston-Werner released Jekyll, a static site generator: you write plain text files, and it turns them into finished pages, with no database behind them. Every visitor gets the same page, and a site that simple gives an attacker less to change. Jekyll started a turn back toward plain sites, helped along because GitHub Pages builds Jekyll sites and hosts them at no extra cost.
For Jess, and for you, these years come down to one rule: match the machine to the job. A page that says the same thing to everyone can be built once and handed to every visitor as it is. Her 1996 page was already that kind of page.
