In the third week, I kept thinking about one question: Am I really showing how a website works?
Later, I gradually realised that I don’t necessarily need to show exactly how the website works internally. What I really want to do is use visual design to make the structure behind the website’s operation something people can perceive.
I was really inspired by Flora’s project last week. She placed transparent sheets with different images on top of each other in different orders, creating different visual effects. This made me wonder: Why can’t I add a Z-axis to the movement traces of text on the website, turning these two-dimensional traces into a three-dimensional space that people can enter?
Once I had this idea, the next steps became quite natural. If I wanted to reveal the movement traces behind the website, I could simply place the normal website in front and the space formed by these traces behind it.
So I created version 14.
version 14 — click to explore
Click inside the window first. Scroll to zoom into the trajectory space, then drag left or right to explore.
Users first see the normal video and annotation interface. But when they try to zoom in, they gradually enter the space of movement traces behind the webpage.
After finishing this version, I suddenly realised that a video is also made up of individual frames. Since I could already organise text traces along the Z-axis, why couldn’t I organise video frames in the same way?
So I started experimenting with arranging video frames along the Z-axis in chronological order, turning a continuously playing video into a space that people could explore. At the same time, the text traces could still pass through different layers of video frames, allowing these two types of information to exist together in the same space.(ITERATION15-18)
Finally, in version 19,
version 19 — click to explore
Click inside the window first. Scroll to zoom into the trajectory space, or hold Space to enter the video slices. Release Space to return.
I kept two different ways of entering these spaces. Users can zoom in to enter the text trace space, or hold down the space bar to enter a space made up of video frames and text traces.
What I want to explore is not how to directly reveal the website’s actual internal structure, but how to turn things that are usually not visible at the same time within one system into a visual space that people can enter and explore.
Looking back at this process, I also noticed something interesting.
At first, programming forced me to translate my visual ideas into positions, sizes, coordinates, and rules. As someone who was used to working directly with images, I found this process quite indirect.
But later, I realised that these abstract parameters and rules were exactly what allowed me to create visual relationships that would be difficult to achieve through traditional two-dimensional graphic design: making images from different moments exist at the same time, allowing traces to pass through video frames, and letting users move between different viewing spaces.
This made me rethink the relationship between programming and design. Programming is not just a tool for turning my existing visual ideas into reality. Instead, through understanding and working with technology, I can discover new visual possibilities, and these discoveries can also change my design ideas.

Leave a Reply