Just enough web technology
Choose tools according to the problem — not because the stack sounds impressive.
How a webpage works
When you visit a webpage, a browser requests files from a server, interprets them, and renders an experience you can see and interact with.
Three foundational languages do most of the work.
HTML, CSS, and JavaScript
- HTML gives the page meaning and structure: headings, buttons, forms, navigation, images.
- CSS controls presentation: layout, typography, colour, spacing, responsive behaviour, and many animations.
- JavaScript controls behaviour: opening a menu, validating a form, filtering results, fetching data.
Frontend and backend
The frontend is the part that runs in the browser and that people interact with.
The backend runs on a server. It may authenticate users, apply business rules, communicate with a database, or protect secret credentials.
Not every project needs a backend. A portfolio, campaign page, or small interactive prototype may run entirely in the browser. Add a backend when the experience needs persistent shared data, private operations, accounts, payments, protected API keys, or server-side business logic.
React, TypeScript, and frameworks
React helps build interfaces from reusable components. A button, card, navigation item, or complete search panel can become a component with defined inputs and behaviour.
TypeScript adds type information to JavaScript. It helps the team and tools understand what shape data should have and catches many mistakes earlier.
A framework provides an organised way to build a full application. Next.js, for example, builds on React and adds routing, rendering options, server features, and production conventions.
For a first one-page exercise, a lightweight setup may be easier than a full framework. For a multi-page product with data and accounts, a framework becomes more useful. Choose tools according to the problem — not because the stack sounds impressive.
Node.js, npm, and packages
Node.js lets JavaScript run outside the browser. In frontend projects, it powers development tools, build processes, and sometimes the backend.
npm is a package manager bundled with Node.js. A package is reusable code created by someone else — an icon library, animation library, date utility, or testing tool.
The project’s package.json is a useful map. It lists dependencies and named scripts such as dev, build, or test.
$ npm install
Downloads the packages already listed by the project.
$ npm install motion
Adds a new package to the project.
$ npm run dev
Runs a script named dev, usually starting the local development server.
APIs, JSON, and databases
An API is a contract for software communication. Your app sends a request to an endpoint; another system sends back a response.
Common HTTP methods:
GETreads data;POSTcreates data or triggers an action;PATCHupdates part of something;DELETEremoves something.
JSON is a common text format for exchanging structured data:
{
"title": "Five-minute reset",
"duration": 5,
"energy": "low"
}
A database stores structured information so it can be retrieved and changed later. A prototype whose data never needs to persist may not need one. Browser storage can remember simple personal preferences on one device. A shared product normally needs a proper backend and database.
Localhost, GitHub, and deployment
Localhost means the app is running on your own computer. It is visible to you but not automatically to everyone else.
GitHub stores the project’s Git repository online and supports collaboration. It does not automatically make every application a public website.
Deployment builds the project and hosts it on an internet-connected service. Platforms such as Vercel can connect to GitHub, deploy each update, and provide a shareable URL.
| Project | Start with | Add only if needed |
|---|---|---|
| Static information page | HTML/CSS or a simple React project | Motion library, analytics |
| Polished interactive landing page | React + TypeScript + CSS | Motion.dev, icon package |
| Multi-page application | Next.js + TypeScript | Component library, backend |
| Product with accounts and shared data | Next.js + backend/database | Authentication, storage, server APIs |
| Story-led animation experience | React + Motion.dev | GSAP for complex timelines or scroll choreography |
- Does your current idea genuinely need a backend?
- Explain npm install and npm run dev in one sentence each.
- What makes localhost different from a deployed website?