Marketing website for Oort Cloud Technology S.L., served at www.oortcloud.tech.
The site is a small set of static, dependency-free HTML pages. There is no build step, framework, or bundler — every page is hand-written HTML with inline CSS and loads instantly.
| File | URL | Purpose |
|---|---|---|
index.html |
/ |
Landing page (services, approach, clients, contact) |
privacy-policy.html |
/privacy-policy.html |
Privacy & cookie policy |
404.html |
served on any unknown path | Custom "page not found" page |
Supporting files:
CNAME— the custom domain (www.oortcloud.tech) GitHub Pages serves the site on.
There's no toolchain to install. Either open a file directly:
open index.html…or serve the folder so that root-relative links (/, /privacy-policy.html)
behave exactly as they do in production:
python3 -m http.server 8000
# then visit http://localhost:8000To preview the 404 page locally, navigate to any non-existent path while using a
server that falls back to 404.html, or just open 404.html directly.
The site is deployed with GitHub Pages, served straight from this repository — there is no CI/CD workflow or build artifact.
How it works:
- GitHub Pages is configured to deploy from the
mainbranch, root (/) folder. (Repository → Settings → Pages → Build and deployment → Deploy from a branch.) - Any push to
mainpublishes automatically within a minute or two. - The
CNAMEfile binds the site to the custom domainwww.oortcloud.tech. DNS for that domain points at GitHub Pages. Keep this file in the repo — Pages re-reads it on every deploy, and deleting it unsets the custom domain. 404.htmlis GitHub Pages' built-in convention: it is automatically served (with an HTTP 404 status) for any request that doesn't match a real file.
To publish a change:
git add .
git commit -m "Describe your change"
git push origin mainThen watch the deployment under the repo's Actions tab (GitHub runs an internal "pages build and deployment" job). Once it's green, the live site reflects the change.
- No dependencies, no build. Keep each page self-contained. Styles live in a
<style>block in each page's<head>; fonts load from Google Fonts. - Shared design tokens. Colours and spacing are defined as CSS custom
properties under
:root(e.g.--accent,--ink,--paper). Reuse them so pages stay visually consistent. - Root-relative links. Link between pages with paths like
/and/privacy-policy.htmlso they resolve correctly on the custom domain.