Color scheme

Portfolio and Reflection Report

Your portfolio repository is set up and deploying, but right now it is mostly scaffolding. In this assignment you will turn it into a real, working website by adding a homepage, a stylesheet, and a proper README. These are the first files you will build on all semester, so take the time to get them right. Every future assignment will add to this foundation.

Assignment Instructions

1. Create Your Homepage

Create an index.html file in the root of your repository. This is the front door of your portfolio. It should be a valid HTML document with a proper <!DOCTYPE html>, <html>, <head>, and <body> structure. At a minimum, include the following in the <head>:

  • A <meta charset="utf-8"> tag.
  • A <meta name="viewport" content="width=device-width, initial-scale=1.0"> tag so the page renders correctly on mobile devices.
  • A <title> element with your name and "Portfolio" (for example, "Ammon Anderson – Portfolio").
  • A <link> element that connects to the stylesheet you will create in the next step.

In the <body>, add at least a heading with your name and a short paragraph introducing yourself and the purpose of this site. This does not need to be elaborate. A few sentences are enough. You will add more content throughout the semester.

2. Add Your Stylesheet

Create a css directory in the root of your repository and add a file called main.css inside it. This is where all of your site styles will live. Start with the following base styles to give yourself a clean starting point:


        *,
        *::before,
        *::after {
            box-sizing: border-box;
            margin: 0;
            padding: 0;
        }

        :root {
            --color-bg: #f4f6f8;
            --color-text: #1e293b;
            --color-primary: #006eb6;
            --color-primary-hover: #004f7f;
            --space-sm: 0.5rem;
            --space-md: 1rem;
            --space-lg: 2rem;
            --font-body: system-ui, -apple-system, sans-serif;
        }

        body {
            font-family: var(--font-body);
            color: var(--color-text);
            background-color: var(--color-bg);
            line-height: 1.6;
            padding: var(--space-lg);
        }

        a {
            color: var(--color-primary);
        }

        a:hover {
            color: var(--color-primary-hover);
        }
    

Notice that these starter styles already use the custom properties and var() patterns you learned on the Custom Properties page. Your design tokens live in :root and everything else references them. As the semester progresses you will expand this token set significantly, but this gives you a working foundation. Feel free to adjust the colors or add more styles if you want to make the page your own.

After creating the file, make sure your index.html links to it correctly. The link should look like this:


        <link rel="stylesheet" href="css/main.css">
    

3. Update the README

Your repository already has a README.md file from when you created it on GitHub. Replace its contents with the following template, filling in your own information:


        # WDD 331R Portfolio

        **Student:** Your Full Name
        **Semester:** Current Semester and Year
        **Live Site:** [View Site](https://your-username.github.io/your-repo-name/)

        ## About

        This repository is my portfolio for WDD 331R: Advanced CSS.
        Each week I add new pages and styles as I work through the course
        assignments. The site deploys automatically to GitHub Pages on
        every push to main.

        ## Pages

        - [Home](index.html)
    

Replace the placeholder values with your actual name, the current semester, and the correct URL to your live site. As you add new pages throughout the semester, you will add links to the Pages list so the README serves as a table of contents for your work.

4. Commit, Push, and Verify

Stage all of your new and modified files, commit with a descriptive message, and push to GitHub:


        git add -A
        git commit -m "Add homepage, stylesheet, and README"
        git push origin main
    

After pushing, go to the Actions tab in your GitHub repository and confirm the deployment workflow completes with a green checkmark. Then visit your live site URL and verify that your homepage loads with the styles applied. If the page shows but the styles are missing, double check that the <link> element in your HTML matches the actual path to your CSS file.

File Structure Check

At this point your repository should have at least these files. You may also have a .gitignore or other files from when you initialized the repo, but these are the ones you created or modified in this assignment.


        [portfolio]
        ├── .github/
        │   └── workflows/
        │       └── deploy-website.yml              # New
        ├── css/
        │   └── main.css                            # New
        ├── index.html                                  # New
        └── README.md                                   # New
    

Submission

Complete the report below with your site details and a brief reflection on what you learned this week. When you are finished, click the download button to generate a PDF and submit it to Canvas.

Portfolio Report
Site Details

My live portfolio homepage is at and the source code is at .

Reflections
Write a thoughtful response to each prompt. Think about how these concepts connect to real projects and your future career, not just what you did this week.

You used custom properties to define a small set of design tokens in your starter stylesheet. Imagine a teammate joins your project six months from now and needs to add a dark mode. Explain how the token structure you set up would help or hinder that effort, and what you would change:

Look at the starter CSS you added to your portfolio. Identify one value that is still hard coded (not using a custom property) that probably should be a token. Explain why extracting it would matter in a larger project:

Browse one professional website you admire and open DevTools. Do they use custom properties? Describe what you found and one thing you would do differently based on what you learned this week: