{"canonical_url":"https://engineer.company/glossary/website/","content_markdown":"# Website\n\n## What it is\n\nA website is a group of related web pages published together for a common\npurpose by an owner or group: a company's pages, a shop, a set of\ndocumentation, a personal blog. The pages often share a domain or a part of\none, a navigation, a look and somebody who answers for them. “Site” is the\neveryday short form, and “web site”, as two words, is the older spelling.\n\nThe useful line runs between the site and the page. WCAG defines a web page as\na non-embedded resource fetched from a single URI over HTTP, together with\neverything a user agent renders with it, such as images, style sheets and\nscripts. Its word for a website is a _set of web pages_: pages that share a\ncommon purpose and come from the same author, group or organisation. That\nsecond definition is the more honest of the two, because it ties a site to\npurpose and authorship rather than to a domain name.\n\nThe examples attached to the definition show how far the idea reaches. A shop's\ncheckout, stripped of the navigation the product pages share, is no part of the\nset those pages form. A blog on a subdomain with its own navigation and its own\nauthors is a separate set from the pages on the main domain. And different\nlanguage versions of the same pages count as different sets. Three domains can\ntherefore hold one website, and one domain can hold several.\n\nThree neighbours get confused with a website. A _web server_ is the program\nthat answers requests; one server can hold dozens of sites, and one large site\ncan be spread across many servers. A _domain_ is the name in the address,\nwhich a site may share with others or spread across several. A _web\napplication_ is a site that provides software through the web, with work done\nin the browser, on the server or both; WCAG's own example is a webmail program\nthat lives at a single address yet shows an inbox, contacts and a calendar,\nwhich makes one URI feel like many pages.\n\nSites also differ in when their pages are made. A _static_ site is generated\nahead of time into files that a server hands out unchanged. A _dynamic_ site\nbuilds each page when it is asked for, usually from a database and a program\nrunning on the server. A reader can rarely tell which is which from the page\nitself. The difference shows up in what has to keep running.\n\n## Why it matters\n\nPeople judge sites, not pages. A reader who lands on one article from a search\nresult decides whether to trust it from what the menu, the neighbouring pages\nand the contact details say. A strong page on a site that looks abandoned\ninherits the abandonment.\n\n**Search engines read the site as a whole.** They index pages one at a time\nbut learn about them through the site: its links, its structure and the list\nof addresses it publishes. The sitemaps protocol, the format a site uses to\nhand that list to crawlers, allows up to 50,000 addresses and 50MB\nuncompressed per file, and a larger site splits its list across several files\ngathered in an index.\n\n**Some accessibility requirements only exist across pages.** Three WCAG 2.2\nsuccess criteria at level AA are written about a set of web pages. Multiple\nWays (2.4.5) asks for more than one route to each page, except a page that is\na result of, or step in, a process, such as a checkout. Routes can be a menu\nand a search, or a table of contents and links between related pages.\nConsistent Navigation (3.2.3) asks that navigation repeated on several pages\nkeep the same relative order each time, unless the user initiates a change.\nConsistent Identification (3.2.4) asks that components with the same job be\nidentified consistently. Every page can pass a check on its own while the site\nfails all three.\n\n**Addresses are a promise.** Each published address ends up in bookmarks,\nother people's links, search indexes, emails and printed material. A site's\nlist of addresses is the part outsiders build on, and it outlives any design.\n\n**Something has to keep running.** A dynamic site is a program with a database\nbehind it, to be patched, watched and paid for every month. A static site is a\nset of files and a server that hands them out. That choice sets the attack\nsurface and the running bill far more than the visual design does.\n\n## What it looks like in practice\n\nThis website is a working example of the definitions above. Built as a\n[multilingual static site in Hugo](/portfolio/built-a-multilingual-hugo-site-in-3-languages/),\nat the stage documented in August 2026 it had 108 template files, 53 of them\npartials and 18 shortcodes, generating three languages from one content tree\nwith no runtime backend. Every page went out in four representations: HTML, a\nMarkdown twin, a Gemini document and a Gopher menu entry. The same tree was\nbuilt seven more times, once per focused subdomain, by pointing the generator\nat a different content directory. Counted by addresses, that was eight sites;\ncounted the way WCAG counts, with each language a separate set of web pages,\nthe three languages alone were three. The page is plain about the price of\nhaving no runtime backend: apart from one scoped JavaScript enhancement for\nthe portfolio filter, interaction was solved at build time or left out, and a\nsearch index was costed and parked for that reason.\n\nThe earlier work shows the other two halves of the job: running sites and\nbuilding them from a design. On the hosting side,\n[forty websites on Ubuntu Linux hosting servers](/portfolio/administered-40-websites-on-apache-and-nginx/)\nran on a mix of Apache and Nginx and were kept available and fast through\nconfiguration, performance tuning and maintenance. The measure there was\nbehaviour under real traffic, since a site that only holds up on a quiet night\nhas been left alone rather than looked after.\n\nOn the building side,\n[thirty websites designed from Photoshop files](/portfolio/designed-30-websites-from-photoshop-to-html/)\nwere converted to HTML by hand and held to two standards at once: faithful to\nthe spacing, type and details the designer intended, and still maintainable once\nthe content started to change. A site that matches its mockup exactly and breaks\nat the first edit was built for the launch, not for the years after it.\n\n## Where it goes wrong\n\n- **A redesign changes the addresses.** Every inbound link, bookmark and\n  search result that pointed at the old structure lands on an error page the\n  day the new site goes live. A permanent redirect from each old address to\n  its new home, kept for years, preserves what other people built on.\n- **Navigation drifts from section to section.** Templates written at\n  different times grow their own menus in different orders, and the same page\n  is called “Contact” in one place and “Get in touch” in another. Readers lose\n  their bearings and the site fails Consistent Navigation and Consistent\n  Identification while every page passes alone. One shared navigation\n  template, used everywhere, removes the drift at its source.\n- **The site is treated as finished at launch.** Content goes stale,\n  dependencies age, certificates expire and the one person who knew how to\n  publish moves on. A site lasts when it has an owner, a publishing routine and\n  checks that run whether or not anyone remembers them.\n- **A page can be reached by one route only.** A page buried three menus deep\n  and left out of every index is found by its author and by very few others.\n  A second route, whether a search, a site map or links from related pages, is\n  what Multiple Ways asks for on pages outside a process, and what readers\n  reach for anyway.\n- **A second language is bolted on after launch.** Addresses, dates, number\n  formats, string lengths and menus were all shaped around one language, and\n  the new one has to fight every template. A site meant to be multilingual is\n  cheaper to build that way from its first page.\n\n## Further reading\n\n- [NIST CSRC Glossary: website](https://csrc.nist.gov/glossary/term/website)\n  — a one-line definition from NISTIR 7693: related web pages prepared and\n  maintained as a collection in support of a single purpose.\n- [WCAG 2.2: set of web pages](https://www.w3.org/TR/WCAG22/#dfn-set-of-web-pages)\n  — the standard's definition of a site by purpose and author, with examples\n  covering checkouts, subdomains and language versions.\n- [Understanding SC 3.2.3: Consistent Navigation](https://www.w3.org/WAI/WCAG22/Understanding/consistent-navigation.html)\n  — why navigation repeated across pages should keep its order, and the\n  failure that breaks it.\n- [Understanding SC 2.4.5: Multiple Ways](https://www.w3.org/WAI/WCAG22/Understanding/multiple-ways.html)\n  — the routes a site can offer to each of its pages, and the exception for\n  steps in a process.\n- [sitemaps.org: Sitemaps XML format](https://www.sitemaps.org/protocol.html)\n  — the format a site uses to list its own addresses for search engines, with\n  its size limits per file.\n- [W3C: Mobile Web Application Best Practices, Web Application](https://www.w3.org/TR/mwabp/#webapp-defined)\n  — the Recommendation's scope includes applications using server-side or\n  client-side processing, rather than requiring browser-only execution.\n\n\u003chttps://engineer.company/glossary/website/\u003e\n","date_modified":"2026-11-09T21:50:25Z","description":"One owner, one purpose, many pages: what makes a website more than its pages, and why its list of addresses is a promise to keep.","formats":{"gemtext":"https://engineer.company/glossary/website/index.gmi","gopher":"https://engineer.company/glossary/website/gophermap","html":"https://engineer.company/glossary/website/","json":"https://engineer.company/glossary/website/index.json","markdown":"https://engineer.company/glossary/website/index.md","pdf":"https://engineer.company/glossary/website/index.pdf"},"kind":"page","language":"en","title":"What is a website?","url":"https://engineer.company/glossary/website/","version":1}