|
| 1 | +--- |
| 2 | +layout: post |
| 3 | +categories: |
| 4 | +- Contribution |
| 5 | +author: Marcus Otto |
| 6 | +--- |
| 7 | + |
| 8 | +## Thing I Contributed To |
| 9 | + |
| 10 | +[CSHPublicSite](https://github.com/ComputerScienceHouse/CSHPublicSite) |
| 11 | + |
| 12 | +> A project that serves as the public-facing website for Computer Science House, showcasing events, members, and the community's history. |
| 13 | +
|
| 14 | +### Why I Picked It |
| 15 | + |
| 16 | +This was my first contribution to a Computer Science House (CSH) open source project. Even though I’ve been a member of CSH for a while, I hadn’t previously taken the time to get involved in any of our open source projects. I chose this one because I’ve been browsing the [CSHPublicSite repo](https://github.com/ComputerScienceHouse/CSHPublicSite) for a while, and I noticed a section on the site that mentioned "one project per freshman", a tradition that hasn’t been active for some time. Since it misrepresents what new members actually experience, I figured this would be a good first fix to get my feet wet with contributing. |
| 17 | + |
| 18 | +### Getting Involved |
| 19 | + |
| 20 | +The process of jumping in was smoother than I expected. The readme made it clear how to install dependencies and preview the site locally using [Jekyll](https://jekyllrb.com/docs/). I followed the setup instructions and was able to spin up a local server. What stood out to me was that the project was well-organized. SCSS partials were modular, assets were clearly separated, and the HTML was easy to follow. I didn't have to dig through complex React states or JS-heavy templates. It felt very welcoming to a beginner contributor. The maintainers of the project were also responsive to me, but I am a member of CSH so that may affect how easy it is to contribute. |
| 21 | + |
| 22 | +### The Issue |
| 23 | +While reading through the about page, I noticed that there was still a section about "one project per freshman". This isn’t current anymore, and having it publicly listed could mislead prospective members. There wasn’t a pre-existing GitHub Issue filed for this. |
| 24 | + |
| 25 | +### The Fix |
| 26 | +I removed the HTML section referencing the outdated freshman project requirement from the homepage content. Specifically, I edited the about/projects.html file and deleted the paragraph block. |
| 27 | + |
| 28 | + |
| 29 | + |
| 30 | +Here’s the relevant [commit](https://github.com/ComputerScienceHouse/CSHPublicSite/commit/8eefa80d0ea59f055c79db2df572dbe24c03874b) |
| 31 | + |
| 32 | +The [PR](https://github.com/ComputerScienceHouse/CSHPublicSite/pull/360) was titled: |
| 33 | + |
| 34 | +Deleted one project per freshman to align with current practice |
| 35 | + |
| 36 | +And here’s a snippet of my pull request comment: |
| 37 | + |
| 38 | +“We haven't done one project per freshman since I've been here, so it would probably be a good idea to remove it from the pubsite.” |
| 39 | + |
| 40 | +This is what the website looked like before my changes. |
| 41 | + |
| 42 | + |
| 43 | +This is what it looked like after my changes. |
| 44 | + |
| 45 | + |
| 46 | +### Was It a Solid Effort? |
| 47 | +Yes, I believe this contribution was appropriate and valuable. It didn’t require a complex code change, but it improved the accuracy and professionalism of our public-facing content. I verified the local build after the change and checked for any rendering issues. |
| 48 | + |
| 49 | +### Was It Accepted? |
| 50 | +Not yet, I am still awaiting a response from our webmasters. |
0 commit comments