Portfolio Site Setup
Before you start writing CSS you need a reliable set of tools and a place to publish your work. This page walks you through installing the software you will use all semester, creating a GitHub repository for your portfolio, and deploying it to a live URL with GitHub Pages. Take the time to get everything working now so you can focus on CSS in the units ahead.
This course uses one public GitHub repository for the whole semester. It is your portfolio: a live site where weekly assignments become evidence of your CSS skills.
Early Semester (Units 1 to 5): focus on completing assignments and building solid architecture. The site may look like a developer log. That is expected.
Late Semester (Units 6 to 7): you stay in the same repository. Unit 6 is the last new CSS. You start the Unit 7 featured case-study page during Unit 6 and submit it in Unit 7. No second repo.
You can organize the catalog earlier if you want: grouped links, featured work, or theme-based sections are welcome any time. A flat assignment list stays valid. Unit 7 adds a featured Build an Unofficial Homepage page, not a required catalog overhaul.
Required Software
Most of you likely have some of these tools installed already. Verify each one and install anything that is missing. All of the software below is free and available for Windows, macOS, and Linux.
Visual Studio Code
Visual Studio Code (VS Code) is the code editor you will use throughout this course. It provides excellent support for HTML, CSS, and JavaScript, includes an integrated terminal, and has a large extension ecosystem. Download and install it from code.visualstudio.com. After installation, launch VS Code to confirm it opens correctly.
Git
Git is the version control system that tracks changes to your files and lets you push your work to GitHub. If you do not already have Git installed, download it from git-scm.com and run the installer with the default settings. After installation, open a terminal and verify it is available:
You should see a version number. If you get a "command not found" error, restart your terminal or computer so the system picks up the new installation.
Node.js
You will not use Node.js right away. You will need it for one Unit 2 assignment when you try CSS build tools like PostCSS and Lightning CSS. After that week a bundler is optional. Installing Node now gives you time to troubleshoot if anything goes wrong. Download the LTS (Long Term Support) version from nodejs.org and run the installer. The LTS version is the stable, well-tested release recommended for most users. After installation, verify both Node.js and npm (which comes bundled with it) are working:
node --version
npm --version
Each command should display a version number. If either one returns an error, restart your terminal or computer and try again.
Never store Git repositories inside folders that sync to a cloud service like OneDrive, iCloud, Google Drive, or Dropbox. Cloud sync tools modify files behind the scenes and will corrupt your Git history. Keep your repositories in a plain local folder such as ~/projects or C:\projects.
GitHub Account and Student Benefits
If you do not already have a GitHub account, create one at github.com. Use a professional username that you would be comfortable sharing with an employer since your portfolio will be publicly visible.
As a student you can apply for the GitHub Student Developer Pack, which gives you free access to GitHub Pro and a collection of developer tools. When the application asks for proof of enrollment, use web.byui.edu/verify to generate the verification document you will need. This step is optional but recommended.
Creating Your Portfolio Repository
Your portfolio needs its own public repository on GitHub. Follow these steps to create it and get your first commit pushed.
Create the Repository on GitHub
Go to github.com/new and fill in the following:
-
Repository Name: Choose something short and descriptive, such as
wdd331-portfolio. - Visibility: Public (required so your instructor and teammates can see your work).
- Initialize with a README: Check this box. You will update the README later as part of your first assignment.
Click Create Repository.
Clone the Repository Locally
On your new repository page, click the green Code button and copy the HTTPS URL. Then open a terminal, navigate to the local folder where you want to keep your projects, and clone the repository:
# This is just an EXAMPLE not actual commands you should run
cd ~/projects
git clone https://github.com/your-username/wdd331-portfolio.git
cd wdd331-portfolio
Replace your-username and wdd331-portfolio with your actual GitHub username and repository name. You now have a local copy of the repository ready to work in.
Deploying with GitHub Pages
GitHub Pages will host your portfolio at a public URL. Your repository itself is the website: the root contains an index.html and subdirectories organize your pages. There is no build step or static site generator involved at first. You write plain HTML, CSS, and JavaScript, push to GitHub, and your site goes live.
In a professional setting you would typically keep source files and production output separate using a build tool. For this course your repository doubles as the live site so you can focus on CSS without extra tooling overhead at the start. You will explore build tools in Unit 2.
Add the Workflow File
Instead of deploying from your main branch directly, you will use a GitHub Actions workflow that copies your files to a separate website branch. This keeps your working branch and your deployed output cleanly separated. Create the folder path .github/workflows/ inside your repository and add a file called deploy-website.yml with the following contents:
name: Deploy Website
on:
push:
branches:
- main
permissions:
contents: write
jobs:
deploy:
concurrency: ci-${{ github.ref }}
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v6
- name: Deploy
uses: JamesIves/github-pages-deploy-action@v4
with:
folder: .
branch: website
clean: true
Push and Trigger the First Build
Commit the workflow file and push everything to GitHub:
git add -A
git commit -m "Add deploy workflow"
git push origin main
This push triggers the workflow for the first time. It will copy the contents of your repository to a website branch that GitHub Pages will serve from.
Configure GitHub Pages
After the workflow finishes, tell GitHub Pages where to find your site:
- In your repository, go to Settings → Pages.
- Under Source, select Deploy from a Branch.
- Set the branch to website and the folder to / (root).
- Click Save.
Your site should be live within a few minutes at a URL like https://your-username.github.io/wdd331-portfolio/.
Verify Your Deployment
Visit the Actions tab in your repository and confirm the workflow completed with a green checkmark. Then open your live URL in a browser to make sure the page loads. From this point forward, every push to main will automatically copy your latest files to the website branch and redeploy your site.
Troubleshooting
If your site does not appear or the workflow fails, check these common issues:
- Workflow Failed: Open the Actions tab, click the failed run, and read the log for the step that errored. The most common cause is a typo in the workflow YAML file. YAML is sensitive to indentation, so make sure every line is indented with spaces, not tabs.
-
No Website Branch: The
websitebranch is created automatically by the workflow on its first successful run. If it does not exist, the workflow has not completed successfully yet. Check the Actions tab for errors. -
Pages Shows a 404: Confirm that GitHub Pages is set to deploy from the
websitebranch at the root folder. Also verify that the workflow ran successfully and that thewebsitebranch contains files. -
Changes Not Showing Up: GitHub Pages can take a few minutes to propagate after a deployment. Try a hard refresh (
Ctrl+Shift+RorCmd+Shift+R) to clear your browser cache. If the old content persists after several minutes, check the Actions tab to confirm the latest push triggered a new deployment. -
Command Not Found Errors: If
git,node, ornpmare not recognized after installation, restart your terminal or computer so the system refreshes its environment variables.
If you continue to experience issues after trying these solutions, reach out to your instructor or teammates for help. Getting your environment set up correctly now saves significant time later in the course.