Semester 2

Week 12

Apple Magic
Cmd

This week was Open Studio, and I was really looking forward to it. But, unfortunately, I got sick and could only attend the first day. That was a bummer. The rest of the week, I tried to catch up on CPJ and worked on some coding for it. Not the most productive week, but I did what I could.

Looking at my Open Studio setup, I noticed that many people had a lot on their tables. Mine felt pretty empty with just two items. I had to keep reminding myself that my project is focused, and it's okay to keep the display simple. Quality over quantity!!!!!!!!!!!!! But still, I couldn't help but wonder if I should have added more, however Vikas did say to add some sketch I did in Sem1 but it was too late as the weekend I am fully busy with errands...

Cmd

Now, about my publication—I realized there's an issue with the paper choice. I used 100gsm paper, thinking it would be light enough, but for the binding method I used, it feels a bit too thick. When I flip through the pages, the whole thing flops over more than I'd like. Maybe switching to a lighter, newspaper-like paper would give it that crisp, effortless flip I'm aiming for. Plus, lighter paper might suit the binding better and prevent that floppy feel.

Then there's the user testing website. After some thought, I'm not entirely happy with its current look. It doesn't quite match the style of my visual compendium, and consistency is key, especially for my portfolio. So, I sketched out a new design to align it more with the compendium's style. The main changes are subtle—switching the border lines to dotted ones and updating the font to match the overall vibe. (Week16 reading this, I did not managed to do the dotted lines as somehow it causes the website to have two different thickness of stroke so I can't figure out the code so I just use a 0.25px line)

Cmd

I also thought about expanding the website's functionality. (Btw if you're reading this Vikas, or anyone, this is me in week 16, I did not managed to code the expansion of the website, I did explain in the further weeks why I did not but I would like to make it clear that the expansion of website had too much javascript to deal with and I am not familiar with Javascript very well, I do understand some parts of my JS code but not all of it, also if I were to asked Chatgpt's help for the expansion, it would be impossible because I am not too sure why when I prompt chatgpt with my code, they will somehow remove my some parts of my code which makes me do more work by troubleshooting and figuring out what is missing in the code so coding this user testing website was such a pain in the ass. Like I actually mean it) In the new design, when users click on an arrow button within a box, it would take them to a dedicated page focusing solely on a specific typographic element, like 'kerning' or 'leading'. This page would offer more in-depth interaction, allowing users to adjust the selected typographic feature more extensively with sliders. For example, beyond just tweaking font size, users could play around with kerning values or change the font weight within the same font family. This would provide a more immersive and educational experience for those exploring typographic principles.

Now that Open Studio is over, I've realized there's still a lot to do. First, I want to expand the publication by adding more explorations—aiming for at least 20 in total. It's important that each page not only showcases a unique typographic experiment but also includes the corresponding p5.js code, so readers can engage with the digital aspect interactively.

I also need to develop the landing page for my CPJ. This means refining the body of work from Semester 2 to include the various explorations I did during that time. Documenting these comprehensively will provide a fuller picture of my design journey and how my ideas have evolved.

Also, I'm thinking about creating another publication about documenting the progression of this project. It would serve as a reflective piece, capturing the challenges I faced, the solutions I came up with, and the overall trajectory of the work. With only four weeks left, the workload feels pretty hefty. But I'm determined to do each task slowly and surely to ensure the final outputs are meaningful and truly represent the effort I've put in. Next week, I will start with the coding of the website and also the content of my documentation for my next publication.