What can someone learn in a quick scan?
I started the revamp after asking a former professor for advice in September 2026. My original site gave long project summaries nearly the same visual weight. A recruiter scanning the page had few cues about where to look or which work to open.
As I revise the site, I ask people what catches their eye and where they lose the thread. Their feedback made me rethink the order of the project pages, so I bring the question and a concrete example forward and leave the build details for readers who want to go deeper. When I disagree with a suggestion, I come back to the same question: will this change make the work easier to understand?
How one project page changed
Follow the Course Assistant page from the original write-up through the first mockup to the finalized design.
I told the story in the order I built it. To find out how the assistant handled a scheduling conflict, readers had to work through the background and development history first.
For layout and presentation, I looked at Lumafield, SVG Tutorial, and growingSWE. I also browsed Supahero, CTA Gallery, and Navbar Gallery for openings, calls to action, and navigation.
One framework, different ways to show the work
I start with a specific question, bring forward an example that helps answer it, and explain what the evidence supports. I add numbers when they clarify the scale, result, or constraint. The format follows the work.
Prototype demo
What happens when none of the 4 finance courses fit a student’s schedule? The demo shows the related option the assistant suggested and explains why I used sample data.
Statistical analysis
The gallery opens on the loudness scatterplot. The page puts the model’s 2.2% explained variation in context so a reader can judge how useful it is for forecasting.
Systems plan
A data-flow diagram follows a meal rating to the feedback manager. A vertical timeline makes the 28-day delivery estimate easy to scan.
What I’m learning from the redesign
This project challenges me to think about UI, UX, and how I present information together. The clock dial is one example. I have to consider what draws people’s attention, whether they can tell how to switch versions, and whether the comparison makes the design changes clearer.
I’d ask first-time readers to find a project that interests them and explain one decision I made. Where they pause or lose the thread would show me which labels or sections still need work.