Learning Outcome
Bring the course together with consistent repository and asset organisation, README documentation, version history and separate backups, testing and link audits, efficient images, small maintenance changes and reliable GitHub Pages publishing.
1Choose a Consistent Structure
website/
├── index.html
├── gallery.html
├── blog.html
├── about.html
├── css/
├── scripts/
└── images/
├── landscapes/
├── portraits/
└── travel/Exact folders matter less than a convention that humans and tools can predict.
2Organise Images Deliberately
- Use meaningful folders and readable, consistent filenames.
- Avoid random assets in the repository root.
- Preserve extensions and exact case.
- Update every HTML, CSS and documentation reference when moving files.
photo.jpg and Photo.JPG may be different deployed files even if a local computer treats them alike.3Document the Project in README
A useful README.md documents what the repository contains, how GitHub Pages publishes it, asset conventions, exact validation commands, and how future branches, reviews and merges should work.
4Audit Links After Moving Files
A moved page or image does not update references automatically. An automated checker can scan local href and src values, resolve them relative to each page and report missing targets. Use a beginner-friendly HTML link checker or project script, document its command, and still click important navigation in a browser.
5Use History and Separate Backups
Git history protects substantially against bad changes: commits reveal differences and can help restore an earlier version. GitHub also holds a remote copy of committed files.
Keep original high-resolution files separately with an appropriate backup strategy; the public repository may contain only derived web copies.
6Optimise Web Images
Export web-sized images instead of full-resolution originals. JPEG suits many photographs; WebP can reduce size where supported. Balance dimensions and compression against visible quality. Smaller files usually load faster, especially on mobile; keep desired originals separately.
7Follow a Maintenance Workflow
A focused branch and commit are understandable; checks and human review reduce risk; GitHub Pages publishes the merge; live feedback guides the next small improvement.
8Final Maintenance Exercise
- Inspect the root for misplaced assets.
- Organise one set if necessary and update every reference.
- Document the convention in
README.md. - Validate links and HTML.
- Commit on a branch, review and merge.
- Verify pages, images and navigation after deployment.
9What You've Built
- a responsive Bootstrap photography website
- source in GitHub and free static hosting through GitHub Pages
- gallery and static-blog foundations
- experience working with ChatGPT and repository-aware Codex
- a basic pull-request workflow and introduction to DevOps principles
- a maintainable repository structure
This is not professional web-development or DevOps certification. It is a practical foundation from which to continue experimenting one purposeful improvement at a time.