Final Project: Capstone CSS Showcase
This is your individual capstone for Advanced CSS. You have practiced modern selectors, layout systems, architecture, frameworks, motion, SVG, and cutting-edge CSS features. Now you get to show it off in one cohesive, polished project that feels like you: your interests, your design taste, and your best technical work.
Pick one of two paths below. Both options are equally valid. Choose the one that excites you and fits your portfolio goals.
Learning Objectives
By completing this project you will:
- Synthesize skills from Units 1 through 6 into a single public deliverable.
- Demonstrate intentional design: modern CSS used with purpose, not a random checklist of tricks.
- Ship accessible, responsive work that holds up on real devices and with reduced motion when applicable.
- Document your choices so an instructor (or future employer) can follow your reasoning.
Option A: Style Stage–Style Challenge (CSS Only)
Style Stage is a community project: every participant styles the same semantic HTML document using only a custom stylesheet (plus optional custom fonts). The HTML is fixed. Your creativity lives entirely in CSS.
For this option, use the official Style Stage source markup (or the current published HTML structure from the project) and write a complete custom stylesheet. You may not change the HTML except where the Style Stage rules explicitly allow (read their contribution guidelines). Your goal is a distinctive visual design that proves you can work inside real-world constraints.
What to submit
-
Host the page in your portfolio so the fixed HTML loads with your CSS. Typical layout:
index.html(Style Stage markup) pluscss/style.css(or similar) linked from your repository. - If you also submit your stylesheet to the public Style Stage gallery, great; that is optional and does not replace the portfolio URL required for this course.
It mirrors how design systems and shared templates work in industry: one structure, many skins. It is an excellent demonstration of cascade, architecture, and visual design without leaning on markup changes.
Option B: Custom Showcase Site
Build your own small site (single scrolling page with clear sections, or a few linked HTML pages) that acts as a showcase of what you learned. Think of it as a guided tour: each major section highlights a course topic you mastered, demonstrated with real components or patterns—not empty claims.
Examples of directions you could take (you are not limited to these):
- A fake product landing page with hero, features grid, testimonials carousel, and themed pricing cards.
- A personal interest site (music, games, hiking, books) with strong typography and imagery.
- A “pattern library” mini-site: each route or section documents one technique (layout, color, motion) with live demos.
You may use plain CSS, or continue with Bootstrap or Tailwind from Unit 4 if you customize deeply enough that the result does not look like a default template. If you use a framework, explain in your reflection how you extended or overrode it.
Course Mastery Checklist (Required)
Whichever option you choose, your submitted work must clearly demonstrate all of the following. Fold them into the design naturally; reviewers should see evidence without a scavenger hunt.
Foundations and architecture (Units 1–2)
- Custom properties for theming or systematic spacing and type (not just one or two variables).
- Organized CSS: clear file structure, layers or logical sections, and a naming approach you can name (BEM, CUBE, utility hybrid, etc.).
Layout (Unit 3)
- CSS Grid and Flexbox used meaningfully in different parts of the project.
-
At least one of: container queries,
grid-template-areas, or subgrid (where supported, with sensible fallback).
Visual design and polish (Unit 4)
- At least two of: transforms, layered gradients, blend modes, or filters—used in service of the design, not as random decoration.
Motion and accessibility (Unit 5)
- Transitions or keyframe animation that support the interface.
-
A correct
@media (prefers-reduced-motion: reduce)strategy so essential content never depends on motion alone.
Icons, SVG, and advanced CSS (Unit 6)
- Inline SVG, a small icon set, or purposeful SVG illustration (accessibility considered).
-
At least one of: scroll snap, or relative color syntax (
oklch(from …)orrgb(from …)) tied to custom properties—with fallback or progressive enhancement if needed for older browsers.
A smaller page executed beautifully beats a sprawling page with thin examples. The checklist is about demonstrated mastery, not ticking boxes in separate disconnected iframes.
Technical Requirements
- Valid, semantic HTML5. Meaningful headings, landmarks, and labels for interactive controls.
- Responsive from narrow phone widths to wide desktop; no horizontal scrollbars unless intentional (e.g. a controlled carousel).
- Hosted in your existing GitHub Pages portfolio with a stable URL.
- All assets load on the live site (no broken images or 404 CSS). Test in a private browsing window.
Portfolio Location
Add a dedicated folder for this capstone so it is easy to grade and share:
portfolio/
└── unit-6/
└── capstone-css-showcase/
├── index.html
├── css/
│ └── (your stylesheets)
└── (optional: images/, js/ if needed)
If Option B uses multiple pages, keep them inside capstone-css-showcase/ and link from index.html.
Your main entry URL for submission should be:
https://<username>.github.io/portfolio/unit-6/capstone-css-showcase/
Submission
Complete the form below, download the PDF, and submit it to Canvas along with your portfolio link. Your instructor will assess the mastery checklist against your live site and repository; this report is for your URL, a short summary, and reflection—not a duplicate write-up of every requirement.
State whether you chose Option A (Style Stage markup) or Option B (custom showcase). In one or two short paragraphs, describe what you built and how it demonstrates the course mastery checklist at a high level. Point to specific sections or components on the live page where helpful.
What are you most proud of on this project? What was hardest, and what would you refine with more time?
Evaluation Criteria
Submissions are judged holistically. Strong work typically shows:
- Mastery checklist: all required areas are clearly present and integrated.
- Design cohesion: typography, color, spacing, and motion feel like one system.
- Accessibility and responsiveness: usable for keyboard and screen reader users, readable on small screens, respectful of reduced motion.
- Code quality: maintainable structure, sensible naming, no obvious unused dead CSS at first glance.
- Live site works: portfolio URL loads complete styling and assets.
Academic Integrity
Follow your course and department policies on collaboration and AI. If you adapt code or take inspiration from Style Stage examples, tutorials, or generative tools, cite them in your reflection and ensure the submitted work represents your understanding and creative decisions.