Monk.Log

picture of the Monk.Log

During my graduation project I developed a platform that helps front-end developers share project progress in a clear and easy way. The goal was to lower the threshold for sharing so the team could learn from each other more easier.

picture of the Monk Log project screen

I started with interviews across the front-end team to get a better picture of how they currently work and share knowledge. That research shaped the concept and direction of the product. Going through sketches, wireframes and user flows was honestly one of the harder parts for me, but getting feedback from a UI designer and my supervisor early helped me move forward with more confidence

The result was Monk.Log. To make logging as effortless as possible I designed a flow where an AI drafts updates based on a developer's weekly Bitbucket commits. I scoped this automation out of the prototype to manage time but the concept was validated and well received.

picture of the Monk Log log screen

This tool has been built with React, TypeScript and Vite. One of my bigger learning curves was data architecture. I started by nesting all data into a single JSON file per project, which quickly became unmanageable. After consulting a senior developer I learned to normalize the data into separate datasets for members, logs and comments. That shift made the system scalable and genuinely ready for back-end integration. I also went through the codebase at the end to align everything with Monks coding standards, which taught me a lot about writing clean and consistent code.

This project has been graded with a 7.5. During this project I learned the value of combining design and technical decisions early and asking for feedback sooner. I didn't have time to polish every detail but I ended with a solid and scalable front-end foundation.

Go up