Home
Welcome to the Hello World wiki.
This wiki is a companion to the Hello World repository - a personal learning platform for exploring GitHub best practices, repository management, and development workflows.
Note
The Hello World Project is for demonstration and learning purposes only.
While the repository README provides a project overview, this wiki serves as a living notebook - capturing deeper notes, decisions, and lessons learned along the way. Think of it as the project's knowledge base, where context and history live alongside the code.
| Page | Description |
|---|---|
| Home | You are here - wiki overview and navigation |
| Part 1 Getting Started | Introduction to GitHub, Git and Visual Studio Code |
| Part 2 Creating a Repository | Creating and configuring a GitHub repository |
| Part 3 Repository Essentials | Markdown, README files, and common repository files |
| Part 4 Branching and Workflows | Cloning, branching, pull requests, and the daily Git workflow |
| Part 5 Working With Repositories | Downloading, referencing, and working with repositories programmatically |
| Part 6 AI as a Learning Companion | AI-assisted coding, GitHub Copilot, and Vibe Coding as a learning companion |
| Part 7 Copilot Configuration | Creating, maintaining, and sharing GitHub Copilot custom instructions |
| Part 8 Field Notes | Practical lessons learned and insights collected through hands-on experience |
| Part 9 Exercises | Companion exercises for each part of the wiki |
| Revision | Revision and change log |
This project is my playground for hands-on learning.
Topics explored so far include:
- Repository structure and organization best practices
- Documentation standards (README, CONTRIBUTING, LICENSE)
- Git workflows, branching strategies, and version control
- GitHub features: Issues, Discussions, Pull Requests, and Wiki
- Editor and tooling configuration (.editorconfig, .gitattributes, .gitignore)
- GitHub Copilot configuration and custom instructions
Following these guidelines is not just about keeping a tidy repository - it is about professional branding. Every public repository is a reflection of how you work. A well-structured, documented, and inclusive repository signals that you care about quality over quantity, and that you invest in making your work accessible and informative to others.
The effort you put into your repos shapes how others perceive you as a professional - do you want to be known as someone who ships sloppy, hard-to-navigate repositories, or as someone who makes a deliberate effort to help others understand and contribute to your work?
For more on building your professional presence, explore the Expand Your Self series on dotjesper.com, including 5 reasons you should share your code and 5 reasons you should promote yourself.
- Repository - source code and project files
- Discussions - questions, ideas, and feedback
- Issues - bug reports and feature requests
- Contributing Guide - how to get involved
For more on the practices used in this project, see these posts on dotjesper.com:
- How to name your PowerShell scripts and functions
- How to validate and improve your PowerShell scripts
- How to set up a well-configured repository
Page revised: March 10, 2026
