Web Dev

Final Project

Goals

Create a project on the web that

  • combines multiple skills and technologies we’ve learned this semester
  • follows the best practices we’ve covered for those technologies
  • stretches you 15-20% past what we’ve already covered / what you know you can accomplish for sure
  • includes a brief (450-750 word) critical reflection on what you built and what you learned from building it
  • you can’t wait to show off to others

Dates

  • Proposal due April 19 at 11:59 p.m.
  • Final submission due April 30 at 11:59 p.m.

Project Menu

Choose one of the following for the final project:

Speculative Redesign

Choose a site you know well, and build it better.

Reorganize the content, add new features, update the visual design, but above all else, make informed choices that actually (or at least arguably) improve the experience of using the site. You should be able to justify your choices based on web design and UX best practices that we’ve discussed throughout the course.

Adventure with JavaScript

Dive into JavaScript and show off what you’ve created in a styled landing page. You might:

  • Complete five projects at javascript30.com and modify them substantially to make them unique (if you choose this project, you’ll have to make some meaningful changes to the JS itself and present it in a compelling way!)
  • Build something cool with an API like GIPHY‘s or OpenWeatherMap
  • Combine a few Codrops tutorials to build something amazing

Agentic AI Exploration 

This project asks: how well can you direct, evaluate, and refine AI as a creative and technical partner?

For this option, you’ll revisit your Project 1 site, but with a twist. Instead of hand-coding it, you’ll use an agentic AI platform – such as Replit, Cursor, Claude, ChatGPT Codex (now free with student accounts) etc. – to recreate your project as closely as possible. The goal is not just to “get something working,” but to match the functionality, structure, and user experience of your original site as closely as you can. If your hand-coded version had a distinct layout or visual design, sticky navigation, and interactions, your AI-built version should too.

This project is as much about process as it is about outcome. You are required to document your entire prompting workflow: your initial prompts, iterations, refinements, and any troubleshooting steps you took along the way. Think of this as a transparent record of how you collaborate with AI to build something real.

Your final reflection should dig into that process. Compare your expectations going into the first prompt with the actual results you got. Where did the AI fall short? Where did it surprise you? What challenges did you run into while trying to get accurate or usable output? You should also reflect on what you learned about writing effective prompts, how your strategy evolved, and what external resources (documentation, forums, tutorials, etc.) helped you along the way.

Grading (25 points total)

Submit your Final Project + Dossier at this Google Form.

Project proposal (0 points / -2 points)

The project proposal will be submitted via this Google Form. If your proposal clearly defines the project you’re considering, you earn 0 points. If your proposal fails to convey a sense of preparation and consideration, you will lose up to two points off your final grade.

Final project (20 points)

The entire final project will be graded qualitatively with an eye specifically toward the project goals. The correct posture for this project is not “What do I need to do?” but rather “How awesome can I make it?”

Specifically, I’ll be looking for thoughtful selection and use of the skills and technologies we’ve learned, designs that follow best practices we’ve covered, independent learnings integrated into the project, and a clear commitment to quality, polished work.

Critical Reflection (2.5 points)

The reflection should be posted to your portfolio, either as a part of your Web Dev course page or as its own subpage. It may also be posted on your final project site itself in a subtle (but clearly discoverable) link in a menu or footer. You’ll submit a link to wherever it lives on the form you use to turn in your final project (see below). It’s also your best chance to guide me through your project make sure I see and understand the amazing work you’ve done.

In roughly 450 to 600 words, walk me through what you built, what you learned from doing so, the challenges you faced, and the things you’re particularly proud of. Make liberal use of screen captures, code samples, and of course, quality, well-edited prose. As always, be as specific and detailed as possible. This is your opportunity to craft a well-supported argument for the grade you think you deserve.

Note: Screenshots are important here, including “work in progress” shots! For example, if you are doing a speculative redesign, show us the original site so we can see how you improved the site design. If you are proud of your custom CSS show us a before and after shot of what the website looked like before you customized it.

Recorded Presentations (2.5 points)

  • Plan on approximately 2-3 minutes for your recorded presentation.
  • The goal is not to give a comprehensive tour of every single part of your site. Instead, aim for the following breakdown:
    • A brief (10-20 second) refresher on topic / goals of your site.
    • 60-120 seconds giving a guided tour of a few (2-4) highlights from your site. These could be design features you’re ready to show off, tricky technical challenges you’re working through, ways you served client needs, etc.

Submission

Submit your Final Project link to this Google Form.