Reference
What is CI/CD?
CI/CD is automating the steps between committing code and it being live: running checks, building, and deploying. For a small site the value is that deployment becomes a repeatable process rather than a person remembering which files to upload.
Also called: continuous integration · continuous deployment
What it removes
- Uploading the wrong files, or forgetting one
- Forgetting to run the build before deploying
- A deploy that works on one machine and not another
- Any deployment step that lives only in someone’s memory
What to put in the pipeline
- Checks that fail the build — broken links, missing meta, regressions
- The build itself
- Generated artefacts such as sitemaps and robots.txt
- Deployment to the host
The version that matters most on a small project
A build that fails on a real regression. A check that fails when a client link dies, or when a page loses its canonical, catches problems in seconds that would otherwise be found by a customer months later.
Where this is covered in depth
A definition can only go so far. Who actually owns your website — a checklist you can verify today covers this properly — 3 minutes, free, no email required.
Who wrote this
Anas Bin Masud builds e-commerce sites and does technical SEO for businesses in the UK, Canada and Pakistan. These definitions come from client work rather than from a content brief — where an entry describes a mistake, it is usually one found on a real site. More about how I work.