DevOps / 06

A delivery path you can inspect.

The same portfolio that describes the workflow uses it: source-controlled changes, automated validation, a static export, and GitHub Pages deployment.

git / github / ci-cd

The workflow

From local change to public artifact.

A static site has fewer moving parts, which makes the delivery contract easy to see.

01

Developer

Implement a focused change against the local TypeScript and component model.

02

Git

Use commits as small, reviewable units of source history.

03

GitHub

Push the branch to a shared, inspectable repository.

04

Pull request

Review the proposed change before it becomes part of the release path.

05

GitHub Actions

Run the repository workflow on a clean hosted runner.

06

Build + type-check

Validate the static Next.js application and generate the export.

07

Static export

Package the out/ directory as the deployable artifact.

08

GitHub Pages

Deploy the artifact to the GitHub Pages environment.

There is no backend process or server runtime in this path. The validation step checks the code and the export; GitHub Pages only serves the generated static files.

Practice notes

Small mechanics, clear intent.

01

Git

A source-of-truth history for deliberate changes, readable commits, and recoverable work.

02

GitHub

A shared repository boundary for collaboration, review, issues, and release visibility.

03

Branches + pull requests

A review surface where implementation choices can be checked before deployment.

04

CI/CD

Automated checks and repeatable delivery reduce the distance between a change and its deployed result.

Compare the runtime diagrams