notes · thoughts ·
Let the content shape the page
Let each project's story guide its structure, and explain why other projects belong beside it. I want a portfolio where familiar navigation leaves room to discover new questions.
Pleasure in reading
Sometimes a portfolio makes its interactions and technical skills easy to notice, but offers little pleasure in reading the work itself. In this site, I want a reader to discover another question within a project and follow it to the next piece.
A fixed structure makes projects easy to compare. Yet one project’s important detail may be the difference between two failed attempts, while another’s is how its initial question changed. Filling the same headings can obscure those differences.
A search project might put results for the same query side by side with the criteria used to judge them. A drawing tool might follow the color and width that persist when tools change. A music note might take its sequence from sounds and sketches. I want to examine what the material explains before choosing how to read it. If a few paragraphs communicate the work well, they may be the right form. An obligation to look different can get in the way too.
A reason to read them together
I think about connections between projects in the same way. Shared tools and categories help readers find other records, but do not explain why two projects are worth reading together. Using React is one kind of common ground; helping readers understand the decisions in each project is another.
A connection needs another sentence. Are these two views of one service, different approaches to preserving state, or similar questions explored under different conditions? A line can suggest more than a relationship: it may imply that an earlier project developed into a later one. I need to distinguish an actual continuation from a comparison I make today.
Archon V1 and V2 have a direct continuation through a renewal of the same service. Rhyme Generator and Foodservice e-commerce search evaluation form a comparison I make today. There is no basis for saying the personal assignment developed into the professional tool.
Reading the two search projects together separates the rules that produce results from the criteria used to judge their usefulness. The rhyme program depends on the final vowel and dictionary coverage. The foodservice e-commerce project’s evaluation tool compares results against the same test set. The projects differ, but both can be read through a question: is producing a result that follows the rules enough?
That comparison is worth keeping. I do not need to claim I held the same question then, or that one project caused the other. I can identify it as a relationship I notice now. Rather than turning the past into one seamless story, I want to leave room for projects that resemble each other without forming a continuous history. Their differences can lead to the next question too.
Familiar paths, different stories
Titles, classification and the way back to the index can stay consistent. Readers should not have to learn the interface again on each page. Within that structure, paragraph order, the weight of images and the form of comparisons can vary with the work.
I choose motion and interaction by the same criterion. They have a purpose when they explain a change or make a sequence perceptible. If they conceal the content or make readers wait, I would remove them. The pleasure can come from seeing something differently after reading.