Purpose

This is not just a book. It’s the visual representation of the whole project and the system behind it. The style guide brings together the concept, the design decisions, and the way the system is meant to work.

It documents the visual language of the project: typography, color, composition, graphic elements, and general rules for application. But it’s not only showing the final result — it’s also showing the logic behind the result. The guide makes the project understandable and consistent. It helps show that the work is not random, but built as a coherent system. It turns individual design choices into something structured, repeatable, and recognizable.

For me, the important part is that the guide represents the whole system, not just one outcome. It shows how different elements relate to each other and how they can be used together. In that sense, it works almost like a visual framework for the project.

Content and Structure

The style guide is a PDF that functions like a manual but maintains flexibility for the future. It covers the core visual elements that define the VorOrt Leitsystem, including typography, color, composition, and graphic elements. I also included general rules for application, so the guide could actually be used — not just admired.

One of the key decisions I made was to take the main shape used throughout the project — the circle — and implement it throughout the whole book. The circle became a structural and visual motif, tying the guide together and reinforcing the system’s identity.

I did my basic research, looking at other style guides through Cosmos and Pinterest to see what worked, what felt too rigid, and what felt too loose. I wanted this guide to feel like a manual but still leave room for future adaptation — something that could grow with the project rather than lock it into one fixed version.

Typography & Signs

My favorite part of the style guide is the typography section. I think it looks really cool because I used the actual sizes that are in the project — not just arbitrary numbers, but the real measurements that would be applied in signage, maps, and other materials. This made the guide feel practical and grounded, not just theoretical.

I also really liked how the signage pages came together, because they showed how the visual language could actually work in application. These pages made the guide feel more concrete and helped connect the rules to real outcomes. I would also like to mention Anna Lena here, who helped me by sharing the margin visuals and related graphic elements that had already been developed for the production team. Including those elements helped strengthen the overall coherence of the book and gave those pages a more finished and connected feeling.

Process and Decisions

The process felt natural to me. I had already helped define the visual direction in the map group, so stepping into the style guide role felt like a logical next step. I wanted the guide to feel clear and usable, not overly technical or intimidating. It’s a manual, but it’s not meant to be strict — it’s meant to be flexible enough for future designers to adapt without losing the core identity.

One of the challenges was translating a visual direction into a guide that others could actually use. It’s one thing to make something look good — it’s another to explain why it looks good and how someone else can recreate that logic. I tried to keep the language clear and the examples practical, so the guide would feel like a tool, not a rulebook.

Outcome and Reflection

I’m happy with the result. The style guide feels like it does what it’s supposed to do: it holds the system together and makes it coherent. It helped bring structure to the larger VorOrt Leitsystem project, and I think it made the whole thing feel more unified.

I learned the importance of a style guide — and of documentation itself. It’s not just about showing what you made — it’s about showing how and why you made it that way. The guide turned my individual design choices into something structured and repeatable, which felt like a real achievement.

Taking over the style guide felt more natural to me than staying in the group map process. I thrive when I can take ownership of a project and keep the momentum going, and this was a perfect example of that. If I could do it again, I’m not sure I’d change much — I’m proud of how it turned out.