Programming and Software Development
Web development
Web development is building for the one platform nobody has to install: the browser. It rests on three languages with separate jobs, HTML for meaning, CSS for presentation and JavaScript for behaviour, and then on the frameworks and browser interfaces layered above them. It is the largest field in software, and also the one where accessibility and performance are most often left until somebody complains.
Why this topic exists: HTML, CSS and JavaScript, then a framework and the browser's APIs: MDN's core and extension modules are the syllabus of the largest development field.
A web page arrives as text. The browser requests it over HTTP, located through DNS and usually encrypted with TLS, then parses the markup into a tree of elements, applies style rules to that tree and runs scripts that can reshape it while the visitor watches. Web development is the work of controlling each of those steps deliberately. Front-end developers own what happens inside the browser; the server that answered belongs to back-end development, and people who do both are called full stack.
MDN's curriculum is the closest the web has to a public syllabus, and its order is telling. The core modules move from structuring content with HTML through three separate stages of CSS to scripting with JavaScript, and only then to frameworks, followed by accessibility, design for developers and version control. Asynchronous code, forms, client-side tooling, performance and testing come later as extensions. Frameworks appear once, late, as one core module among nine.
| Layer | What it decides | What learners skip |
|---|---|---|
| HTML | What each piece of content is: heading, list, button, form field | Semantic elements, replaced with generic containers assistive technology cannot interpret |
| CSS | How content looks and where it sits at every screen width | The cascade and the layout systems, replaced with trial and error until one laptop looks right |
| JavaScript | What happens when the visitor acts, and how data arrives without a reload | Asynchronous code, until two network responses race each other |
| Frameworks | How a large interface splits into components that share state | The document tree underneath, which the framework edits on your behalf |
| Tooling | How source files become what the browser downloads | Reading the build output, until the bundle is far larger than it needs to be |
Frameworks are a choice of trade-offs
React, Vue, Angular and Svelte solve one shared problem: keeping a complex interface consistent with changing data. They differ in how much they decide for you. Angular ships routing, forms and data access as one opinionated package, suited to large teams wanting the same structure in every project. React supplies components and leaves most other choices to its ecosystem, which is why adverts name it beside a list of companions. Vue and Svelte sit between, with gentler learning curves and smaller hiring markets. Server-rendering frameworks built on them, such as Next.js and Nuxt, move part of the work back to the server for speed and search visibility. A design system cuts across all of them as the component library a team builds from.
Accessibility is not a later module
Semantic markup, visible focus, labelled form fields and adequate colour contrast cost almost nothing when written in from the first line and a great deal when retrofitted. A front-end developer who can test a page using only a keyboard and a screen reader brings something many applicants cannot.
freeCodeCamp's Responsive Web Design, JavaScript and Front-End Development Libraries certificates follow broadly the same sequence as MDN and serve well as structure and as evidence of finished projects. A portfolio site you coded yourself, quick on a phone and usable without a mouse, says more than all three. In agency and client work built on a CMS theme or a bought web template, the job shifts from building layouts to adapting and maintaining someone else's.
Next to this topic
- Programming fundamentalsOne language learned properly plus enough of the machine beneath it: variables, control flow, data structures, debugging and reading code (SFIA Programming/software development; MDN's getting-started modules).
- Programming languagesPython, JavaScript, Java, C#, C and C++, Go, TypeScript, Rust, Kotlin, Swift: what each is for and where it is hired, so the first choice is a career decision rather than a syntax preference (Udemy's Programming Languages shelf names the market).
- Back-end development and APIsServers, frameworks, databases behind them and the HTTP and REST contracts between services (MDN server-side modules; DVA-C02; the freeCodeCamp back-end certificate).
- Mobile developmentiOS, Android and the cross-platform frameworks are their own toolchains, stores and review rules (SFIA Systems development; Udemy's Mobile shelf).
- Databases and SQLThe relational model, SQL, schema design and the document and key-value stores next to it: the layer every application and every analyst stands on (SFIA Database design; DP-900 relational concepts).
- Software engineering practiceVersion control, code review, testing habits, architecture, design patterns and clean code: the slow layer hiring quietly filters on (SFIA Systems and software lifecycle engineering; MDN version-control module).
- Software testing and QATesting as a discipline: the ISTQB Foundation syllabus v4.0.1 (fundamentals, testing through the lifecycle, static testing, analysis and design, managing test activities, tools) plus the automation frameworks (Selenium, Cypress, Playwright).
- DevOps, Git and CI/CDVersion control workflows, pipelines, containers for developers and the culture that joins build and run (AZ-400; GitHub Foundations and Actions; the cloud field owns infrastructure as code and operations).
- Game developmentEngines, graphics, physics and the design loop are a development field with its own tooling and job market (Udemy's Game Development shelf; SFIA Animation development).
- No-code and low-code developmentBuilding software without writing most of it (Bubble, Webflow, Zapier, Make, Airtable) is a recognised route into shipping products; Microsoft's Power Platform is the office-suite version of the same idea.
- AI-assisted developmentAssistants changed how fast plausible code appears, not what makes it correct; reading, testing and correcting generated code is now part of the craft (GitHub certifies Copilot use and, on its 2026 credentials page, agentic AI development).
Concepts to know
Glossary entries with the reason each one matters here.
- HTTP
The protocol every page load runs on.
- Web Server
What answers the request the browser sends.
- Template
Buying a starting point is a build decision.
- Design system
Where the front end meets design at scale.
- DNS
The first thing that happens when a URL is typed.
Certifications that test it
Vendor exams and free certificates; facts, cost and the preparation path are on each page, and the certifications hub has them all.
- freeCodeCamp · Online exam, not proctored · freeResponsive Web Design CertificationfreeCodeCamp's free HTML and CSS certificate.
- freeCodeCamp · Online exam, not proctored · freeFront-End Development Libraries CertificationReact and the front-end libraries, free.
- freeCodeCamp · Online exam, not proctored · freeJavaScript CertificationThe language of the browser, certified free.
Guides that apply
- How to choose web hosting
Where the site goes once it is built.
Tools of the trade
- JavaScript
The language of the browser.
- TypeScript
JavaScript with types, now the default for large front ends.
- PHP
WordPress is PHP.
- React
The front-end library most job adverts name.
- Angular
Google's front-end framework for large applications.
- Vue.js
The approachable front-end framework.
- Next.js
React with routing, rendering and a server.
- WordPress
The CMS behind a large share of the web.
Frequently asked
- Should I learn a framework or plain JavaScript first?
- Plain JavaScript, until you can fetch data, update the page and handle an event without help. A framework then reads as a set of conveniences you understand. Starting with the framework tends to leave people stuck the first time its abstraction does something they did not expect.
- What is the difference between web design and web development?
- Design decides what the interface should look like and how people move through it; development makes it work in real browsers with real data. The roles overlap in CSS, layout and accessibility, and many small-studio jobs expect both.
- Do front-end developers need to understand the back end?
- Enough to read an API response, understand status codes and caching, and know why a request failed. Writing the server is a separate job, but a front-end developer who cannot debug the boundary will wait on colleagues for every problem that crosses it.
Courses in the directory
3,429 courses are filed here; the top 6 by our ranking, details and the provider link on each course page.
Last reviewed 26 September 2026 · Getting Digital