Color scheme

Resume with Print CSS and Form

This assignment brings together the two readings from this week. You will build a resume page on your portfolio and write a print stylesheet that makes it look professional on paper, add a small contact form styled with accent-color, and audit your token files for the sprawl the second reading described. Resume and contact are portfolio staples; link them from your homepage when you are ready.

What You Are Building

By the end of this assignment your portfolio will have a printable resume page and a styled contact form. Here is where the new and updated files fit in your existing architecture.


        [portfolio]
        ├── css/
        │   ├── base/
        │   │   └── elements.css         # update: form element base styles
        │   ├── tokens/
        │   │   ├── colors.css           # audit
        │   │   └── variables.css        # audit + update: accent-color
        │   └── main.css                 # update: print block or import
        ├── resume.html                  # new
        ├── contact.html                 # new
        └── README.md                    # update
    

Assignment Instructions

1. Build a Resume Page

Create a new page on your portfolio for your resume or CV. Use semantic HTML to structure the content: headings for section names, lists or description lists for experience entries, and proper heading hierarchy throughout. The content should be real or realistic. Include at least your name, a brief professional summary, education, and work or project experience. If you have volunteer work, leadership roles, or service experience you are welcome to include those as well, but they are not required.

Style the screen version with your existing typography and color tokens so it feels like part of your site. The resume page should look intentional on screen, not like an unstyled document.

2. Write a Print Stylesheet

Add a @media print block (in your main stylesheet or a separate print.css) that makes the resume page print cleanly to PDF. Apply the techniques from the print stylesheet reading: hide navigation and any interactive chrome that has no purpose on paper, switch to a print-appropriate typeface and size in pt, surface link URLs with ::after so they are visible on the printed page, use break-inside: avoid to keep experience entries from splitting across pages, and set orphans and widows so no single line sits alone at the top or bottom of a sheet.

If your resume includes a brand header or section dividers where the background color carries meaning, use print-color-adjust: exact on those specific elements so the color survives printing. Apply it only where the color is genuinely meaningful, not to every element.

Test in print preview in at least two browsers. The submission report asks for a screenshot of both the screen version and the print preview so you can compare them side by side.

3. Add a Contact Form

Build a small contact form on your site. It can live on a dedicated contact page or as a section on an existing page. The form needs at minimum a name field, an email field, and a message textarea, each with a visible <label> element associated to its input through a matching for and id. The form does not need to actually submit anywhere; a stub with proper markup and styling is sufficient for this assignment.

Set accent-color on the form or on your root element so any checkboxes, radio buttons, or range inputs you include pick up your brand color from the token you already have. If your form only contains text inputs and a textarea, add at least one checkbox (such as a "subscribe to updates" toggle) so the accent color is visible.

If the browser supports field-sizing: content, your message textarea should grow with its content. Chrome, Edge, and Safari (from version 26.2) support this property; Firefox does not yet as of this writing. Include the property with min-height and max-height guardrails so it degrades gracefully where unsupported.

4. Audit Your Token Files

Search your variables.css and colors.css for each token name. If a custom property is declared but never appears in a var() reference anywhere else in your CSS, it is an orphan. Remove it. In VS Code, search your project for the token name and exclude the file where it is defined. Zero results outside that file means the token is unused.

Look for near-duplicate values that landed within a pixel or a few percent of each other, such as a --spacing-card at 14px alongside a --spacing-sm at 12px. Decide which value is correct, point every consumer at one token, and delete the other. Then check for naming drift: if both --text-sm and --font-size-sm exist for the same concept, settle on one convention and rename everything to match. A find-and-replace across your CSS directory handles most of it. Test in the browser after each change to make sure nothing breaks.

5. Commit, Push, and Verify

Stage your changes, commit with a descriptive message, and push to GitHub. Update your README.md to note the resume page, the print stylesheet, and the contact form. Verify that your deployment succeeds and that your live site shows both new pages working correctly.

Submission

Complete the report below. When you are finished, download the PDF and submit it to Canvas. Your live site is graded by visiting it directly, so make sure your portfolio is deployed and current.

CV, Print, and Contact Form Report
Site Details

My live resume page is at and the source code is at .

Screenshots

Take a screenshot of your resume page as it appears on screen, then open print preview and take a screenshot of the same page as it will look on paper. Upload both below so the difference is visible.

Screen View
Print Preview
Reflection
Print Decisions

Compare your screen and print versions. What did you change for print and why? Identify one element where hiding, restyling, or adding content (such as surfaced URLs) made the biggest difference to the printed result, and explain the tradeoff you weighed.

Token Audit Results

Describe what you found when you audited your token files. How many orphan tokens, near-duplicates, or naming inconsistencies did you discover, what did you change, and how did the cleanup affect the readability of your token system?

Form Accessibility

Evaluate the accessibility of your contact form. How did you associate each label with its input, and what would a screen reader user experience when navigating your form? If you tested with a screen reader or the browser's accessibility inspector, describe what you found.