Hacks Summary

CSA Hacks Blog

Version Control

While creating my typewriter effect on my homepage, I went through several iterations of my code in order to test out different features, and customize the visualization to make it more minimalistic. I used version control to track how the changes I made were reflected on to my homepage.

I have my repository cloned on my desktop where I can also access my files, however, I typically use WSL when making changes to my site.

The files in my GitHub are updated when I push my changes from VSCode and sync my changes to the repository.

I would use CSS and Javascript to customize the default UI of the ‘portfolio_2025’ to include more features and make the design unique. I would also add a capture page to document screenshots of important teaching moments.

Localhost vs Deployed Server

When cloning my repository in VSCode, I deployed a local host URL by running the command make on my VSCode terminal. This is a local site only to your computer, meaning no one else can see those updates.

When committing and pushing to update your GitHub repository, those changes are updated to your GitHub Pages website. Since this is on a GitHub domain and is public, others can see the updates that you put onto the site.

DNS and GitHub Pages

There is a domain for my GitHub Pages; my website is hosted on github.io.

The URL for each GitHub Page is different. The website follows the syntax of username.github.io/repository_name.