RobotnixAcademy

Unit 08 · lesson

Publish the Portfolio

This is the point where your source becomes publicly reachable.

Treat that as a release, not a casual preview.

Preflight

Before pushing the deployment change:

[ ] working tree reviewed
[ ] no secrets/private data
[ ] production build succeeds locally when practical
[ ] internal links/baseurl strategy reviewed
[ ] images/assets load in generated output
[ ] keyboard/accessibility checks pass
[ ] source commit created
[ ] remote branch is correct

Push source

Use your normal Git workflow to push the reviewed branch/commit to GitHub.

Do not paste credentials into commands or course submissions.

Configure Pages

Follow the current GitHub Pages official instructions for the publishing mode you selected:

  • branch publishing; or
  • GitHub Actions.

If using a custom Jekyll workflow, start from GitHub's current Pages/Jekyll workflow template and read every major step before committing it.

Watch the build/deploy evidence

Do not refresh the website fifty times without looking at the workflow/build state.

Inspect:

  • workflow run status;
  • build logs if failed;
  • deploy step;
  • Pages-reported URL.

First public verification

At the public URL, test:

  • Home;
  • About;
  • Projects index;
  • one project page;
  • Journal;
  • CSS/images;
  • navigation;
  • keyboard focus;
  • page title/metadata.

Record the release

Deployed commit:
Workflow/run:
Public URL:
Deployment mode:
Verification result:

Checkpoint

Your portfolio is not "published" for this course until you can tie the public result to a specific source commit and deployment run/state.