solution bonus b

Solution Reference: Bonus B -- Document Your Journey

This shows an example reflection document.

Example journey reflection

# My Git Going with GitHub Journey

## Before the workshop

I had never used Git or GitHub. I thought "version control" was saving files
as `report-final.docx`, `report-final-v2.docx`, `report-ACTUALLY-final.docx`.

## Day 1: You Belong Here

The scavenger hunt (Challenge 1) made the GitHub interface feel less intimidating.
I learned that a repository is organized like a folder with special powers --
it tracks every change anyone makes.

Filing my first issue (Challenge 2) surprised me. I expected issues to be
complaints, but they are really conversations about improvements. Writing a
clear title forced me to clarify my thinking before I started typing.

The merge conflict (Challenge 7) was the moment everything clicked. Seeing
the conflict markers and understanding that Git was asking ME to make a human
decision -- not failing or breaking -- changed how I think about collaboration.

## Day 2: You Can Build This

Going local (Challenge 10) felt powerful. Having the files on my machine and
using the terminal made me feel like a real developer, even though all I did
was fix a typo.

The code review (Challenge 12) taught me that feedback is a skill. My first
attempt at reviewing was just "looks good" on everything. After reading the
chapter, I went back and left a specific suggestion that my buddy actually
used. That felt collaborative in a way I had not expected.

## What I will do next

- Contribute to an accessibility project on GitHub
- Set up Git on my personal laptop
- Explore GitHub Skills for more practice

## One sentence summary

I came in thinking Git was too technical for me and left knowing it is a
communication tool that anyone can learn.

What matters

The learning objective is structured reflection using proper Markdown. If you wrote a document with headings, paragraphs, and honest reflection, you completed this bonus.