This is the Patchwork brand guide, and its basically how we made our branding “transferable” instead of only living in our heads. It fits LO2 because it documents the logo, colors, typography, and tone of voice so anyone in the team can keep things consistent. I also helped with setting up our Canva work and animations for presentations, so what we showed matched the same style.

link to the brand guide: Patchwork brand guide

This is my Calcifer game document. It fits LO2 because it explains the full concept in a way other people can use not just “the idea”, but the rules, mechanics, and how it should work. That way a teammate (or client) can understand it without me needing to sit next to them.

Here is the document: calcifer

Here you can see Version 1 and Version 2 of the same deliverable (there are 3 versions total, these are the first two). This fits LO2 under version control because I tracked improvements across versions and updated the document using client feedback instead of rewriting from scratch and losing the history.

This links will show you V1 and 2 of document: Version 1
Version 2

This is my GitHub repository for the portfolio website. It fits LO2 because it shows I stored my work in a way that's trackable and reproducible. If something breaks, or I need to return to an older version, Git makes that possible.

Link to the Git: Portfolio Git

This shows Figma's version history. It fits LO2 because it's version control on the design side: I can check earlier versions, compare changes, and understand how the design evolved without losing anything.

This shows our Discord setup for sharing files and keeping everything in one place. It fits LO2 because it supported teamwork: files were easy to find, updates didn’t get lost, and we could share documents quickly without everyone hunting through different folders.

This shows my palette iteration process. I didn't just pick colors once I compared different options, tested contrast, and adjusted until the palette matched the vibe while still being readable. That's why it fits LO3: it's an actual design iteration, not a one-shot decision.

This link goes to figma where it is located: Figma

Here is a clear before/after of removing the funny button. At first I planned something for it, but feedback pointed out that a “funny button that doesn't do anything” is only funny once after that it just feels unfinished. Cutting it improved the UX and made the site feel more complete.

This is the iteration where I removed the statistics bar. Someone pointed out that the stats could be misleading because I can't 100% prove them. So instead of risking questionable info on my portfolio, I removed it and kept the homepage more honest and clean.

This shows how my Calcifer document changed across versions. The concept got shaped by real feedback from Desca, and you can see the connection between each iteration and what was improved. That's exactly what LO3 is about: changes with a reason, not random edits.

here all the iteration will be linked:
Iteration 1
Iteration 2
Iteration 3

This is my GUI redesign after vacation. You can see the “before to after” clearly: layouts got cleaner, components got more consistent, and the whole thing feels closer to a real control panel instead of a rough mock-up.

You can check it out here: Figma

This shows how I made the Events page easier to understand. I got feedback that the page was confusing, so I adjusted it to be clearer (including the colors and the way settings are shown). I received feedback from Wouter, unfortunately I have no way of proving that part, but the before/after shows what changed and why the final version reads better.

This is our team charter. It shows we didn't just “work together” casually we agreed on how we communicate, what we expect from each other, and how we handle responsibilities. That's why it fits LO4: it's a professional setup for how we work.

Teamcharterm pdf : pdf

This shows our Trello planning. We used it to break work into tasks, assign responsibilities, and keep track of what was happening. It fits LO4 because it's part of a structured approach to managing a project as a team.

This shows our Jira board (Scrum). We switched to Jira when we needed a more detailed way to track progress and statuses. It fits LO4 because it shows a professional workflow for planning, doing, and reviewing work in a team setting.

This is our client pitch presentation. The goal was to convince the client why our idea made sense and what value we could deliver. It fits LO4 because it shows stakeholder involvement, clear goals, and professional communication.

Link to the presentation: Pitch presentation

This is Desca meeting 1. We presented our idea, asked questions, and collected feedback directly from the client. It fits LO4 because it shows stakeholder involvement and decision-making based on what the client actually wants.

This is Desca meeting 2. Here we checked progress, confirmed what direction we should keep going in, and made sure the project still fit her needs. It fits LO4 because it shows continuous stakeholder involvement, not just one meeting and done.

This is our prototype presentation. We had to show what we built so far, explain how it works, and communicate what was still missing. It fits LO4 because it's basically reporting progress in a professional way to teachers/stakeholders.

This is the final presentation. Here we delivered the final outcome and explained the reasoning behind our choices. It fits LO4 because it shows final reporting and delivery, not just the build itself.

Here you can find the full presentation: Canva

This is my gamification research document. It fits LO4 because it's applied research: I looked into what makes things engaging and how gamification can influence behavior, and I used that knowledge to support design decisions instead of purely going on vibes.

Read the whole doc here: Gamification Document

This is my game design research document. It fits LO4 because it's research with a goal: I wanted to understand what's realistic and what skills are needed if I move further into game design. It's also advice-oriented, because future students can use it as a starting reference too.

Read the whole doc here: Game design research Document

I did a personal values test to get a clearer view of what I actually stand for and what I naturally prioritize. This fits LO5 because it connects directly to “acting in line with my core values” it helped me put words on what drives me, so I can make better choices during projects instead of just going on autopilot.

Here I have the document fr you to full view but its in the images aswell: My values

I also did a personality test to understand how I work, how I communicate, and what I do under pressure. This connects to LO5 because its about knowing my strengths and weaknesses, and it gives me something concrete to improve on instead of guessing.

I went to Comic Con because I'm a media student and I love games, so I wanted to learn more about the world I'm entering. There were a lot of different artists and styles there, which gave me inspiration and also helped me understand how creative communities work in real life. This fits LO5 because it shows initiative and personal growth outside school.

During the project I kept a paper where I wrote feedback down. It's the same paper I also show at LO4 (prototype presentation). For LO5, it matters because it shows my learning attitude: I don't just hear feedback and forget it I collect it and use it to improve.

I joined a Blender workshop at school to improve my skills in 3D. This fits LO5 because it's a clear example of me pushing my own growth and building confidence in something new, instead of staying only in what I already know.

I attended an Unreal Engine workshop to get more familiar with real game development tools and how they work. This fits LO5 because it connects to my future goals in game design, and it shows I'm actively investing time into learning beyond the minimum.

This semester I had to use my planning skills a lot because I was moving while still trying to keep up with school. At the start it was going okay, but toward the end the planning didn't work anymore and I focused most of my attention on moving. This fits LO5 because it shows self-awareness, and I know what I'd do differently next time: start planning at least a month earlier.

At the beginning of the semester we did retrospectives after sprints, and they were actually helpful. Later on we silently stopped doing them, and I think that played a part in why progress slowed down. This fits LO5 because it's reflection on teamwork habits, and in the future I want to learn how to keep retros going so motivation and alignment don't drop.