Why are we creating a design system for OSM?
Postitas Gustavo22Soares kuupäeval 18. juuni 2025 – English. Viimati uuendatud: 26. juuni 2025.Over the past 20 years, OpenStreetMap has become one of the world’s largest and most impactful crowdsourcing projects. Thousands of communities have formed around collaborative mapping, connecting people and fostering the sharing of geographic knowledge.
Today, OpenStreetMap is an essential source of geographic data, powering a wide range of map services used by thousands of people daily and serving as a vital tool in managing climate and humanitarian crises. Although the main site, OSM.org, is not designed as a direct navigation tool, the experience of new users plays a crucial role in attracting new mappers. Improving usability for the public, therefore, benefits the entire community, alongside the millions of organizations that use OSM data.
In recent years, the OpenStreetMap ecosystem has grown significantly, expanding to every corner of the world and yet, the user interface of OSM.org is much the same as it was when OSM was founded in 2004. Among other challenges, it is not optimized for mobile devices, nor does it meet modern accessibility standards. We believe this is the time to prioritize a more cohesive, intuitive, and enjoyable user experience while making it easier for developers and contributors to create solutions.
To achieve this goal, we are developing a design system, a set of reusable guidelines and components that unify the design and functionality of digital interfaces. This system has been designed to meet the community’s needs, promoting consistency, accessibility, and scalability. It will ensure that interfaces are inclusive, modern, and capable of addressing the needs of a diverse global community.
Discover the Atlas
Atlas will be the design system of OpenStreetMap, designed to unify and modernize the user experience across all platforms. Currently under development, it is intended to be introduced as part of a new version of OSM.org and the OSMF website, bringing consistency, accessibility, and innovation to the global community.
Let’s take a closer look at the design system.
Our principles
A Map for Everyone: Our goal is to create a map for everyone, regardless of ability, language, device, or technical expertise. We aim to eliminate barriers between users and the knowledge OpenStreetMap provides, ensuring that everyone can access and contribute to the map seamlessly.
This involves:
- Accessibility for all, regardless of abilities or limitations.
- Multiple languages and content formats.
- Device and network compatibility with various devices and networks.
- Easy-to-use tools and resources, suitable for non-technologists and technologists alike require no advanced technical knowledge.
-
Representation and respect for all cultures, ethnicities, and genders, ensuring inclusivity and representation for all
In short, we aim to create a map that can be a powerful tool for communities to assert their regional identity while promoting inclusion and diversity. Everyone, regardless of their background or abilities, should feel welcome and empowered to contribute to OpenStreetMap.
Reliable and Consistent: OpenStreetMap must be a trusted source of geographic data, inspiring confidence through its accurate and accessible solutions. Achieving this requires consistency in our designs, ensuring that users can easily navigate and trust the experience we offer.
By using familiar concepts and common patterns, we make OSM intuitive and straightforward to use across platforms, languages, and formats. This helps users feel secure and confident when exploring OSM, knowing they are engaging with a platform that values precision and quality without compromising usability.
Our goal is to remain a reliable source of geographic data while keeping the platform intuitive, accessible, and constantly updated. By maintaining consistency in our design, we ensure that OSM continues to be a valuable, trustworthy tool that provides a high-quality user experience.
Recognition: We want OpenStreetMap to become as recognizable and respected as other free knowledge-sharing software projects, such as Wikipedia. Achieving this level of recognition will attract more local mappers and strengthen the community, positioning OSM as a global reference in collaborative mapping and geographic knowledge sharing.
Reusable components:
Atlas consists of various reusable elements that translate design decisions into tokens, assets, and components. These elements can be used to build interfaces fully aligned with Atlas.
Design tokens: Design tokens are standardized values that represent design decisions, such as colors, typography, spacing, and styles. For example, the token color-accent
may have the value #57814C
or #82BF71
, depending on the applied theme (light or dark). This token is used to define the color of buttons or other highlight elements, ensuring design consistency and simplifying the development process.
Assets: Assets are visual resources that help recognize available actions (icons), promote engagement, or represent our brand/organization (logos). Atlas currently uses the Material Symbols library as the basis for its icons.
Components: Atlas is constantly evolving and continues to expand its component library. Components are combinations of elements and assets styled by design tokens, which can be reused across different products and adapted to various use cases. Currently, components are developed using Svelte and a CSS only version, without requiring JavaScript.
How can this benefit designers, developers, and others?
If you contribute to building applications for the OpenStreetMap (OSM) ecosystem, you might be wondering: how can this benefit me? Our goal is to ensure that everyone working on the front-end can take advantage of a well-structured design system:
-
Consistent experience: Atlas will provide accessible, consistent, and well-tested standards that can be used across the OSM ecosystem. This will result in a more cohesive experience for users. Delivering a great experience, regardless of language, disability, device, browser, or connection speed, is essential for a truly global map.
-
Scalability and flexibility: A well-designed system makes it easier to scale products and features while ensuring that new components and designs are seamlessly integrated. It offers flexibility for customization while maintaining consistency, enabling teams to work efficiently on a variety of projects.
-
No need for modifications: Currently, the front end of OSM.org is built using Bootstrap. While this approach offers benefits like a quick starting point for development, it also introduces challenges. Heavy reliance on Bootstrap styles and classes makes customization difficult, can lead to visual inconsistencies, and adds unnecessary code bloat to projects.
-
Focus on what really matters: Since Atlas is composed of pre-made design decisions, designers and developers can focus their efforts on solving more critical problems for their projects. This eliminates the need to spend time on repetitive basic details, boosting productivity and creativity.
-
Open to collaboration: Our goal is to replicate the core philosophy of OSM, being open and collaborative. You can contribute to both design and development. Currently, we are using Figma as our design tool, but we plan to release a version compatible with Penpot to make collaboration even more accessible to different contributors.
Considerations
When migrating to Atlas there are several factors to consider, as with any transition to modern tools. It’s important to keep in mind that the system is still under development. Before adopting it for a new project or migrating an existing one, evaluate whether Atlas provides the necessary components to meet your project’s needs. Currently, we are focused on supporting web applications, but we plan to expand to mobile platforms in the future.
How I can stay update and contributed?
Atlas is currently a collaborative effort between the University of Brasília and the OSMF Foundation, supported by the Communication Working Group. Our team consists of 10 passionate designers and developers dedicated to this initiative.
We warmly welcome contributions and collaborations from the entire OpenStreetMap community. Whether you’re a designer, developer, or simply interested in our work, there are many ways to get involved or stay updated:
- Subscribe to tasks and join the discussion on our GitHub repository.
- Participate in the design process, whether by creating new components or contributing assets.
- Write and submit code to improve or expand the system.
- Review existing code to ensure quality and consistency.
- Update and enhance the library’s documentation to make it more accessible to all.
Contributions to Atlas are guided by the OSM Code of Conduct, ensuring a respectful and collaborative environment.
We’re thrilled to work together to break down technical barriers to accessing free map data, and we hope you share our excitement!
Atlas will be at STOMUS 2025! Come learn more about the project and find out how you can contribute. If you’re attending the event, don’t miss this chance! see the schedule.
We are proposing this project for funding through the Engineering Microgrants 2025 program. With this support, it will be possible to boost the development of Atlas and make OpenStreetMap more accessible to everyone. So don’t forget to show your support by commenting and sharing the project, your participation could be decisive for it to be selected and funded!
Take a look at our proposal! link
Special thanks to the Wikimedia Codex team, you laid the foundation for this project!
Arutelu
Kommentaar kasutajalt R0bst3r 18. juuni 2025, kell 03:25
Maybe you can join efforts with? osm.wiki/OpenStreetMap-NG
Kommentaar kasutajalt -karlos- 18. juuni 2025, kell 04:24
Seems to be alike the German project for a modern homepage:
https://community.openstreetmap.org/t/relaunch-openstreetmap-de/119539
Kommentaar kasutajalt SimonPoole 18. juuni 2025, kell 07:42
‘millions of organisations’?
Kommentaar kasutajalt TomH 18. juuni 2025, kell 07:47
Maybe you shouldn’t say that this “will be the design system of OpenStreetMap” before you’ve actually got any sort of agreement on that?
Kommentaar kasutajalt Wynndale 18. juuni 2025, kell 07:55
Is there a demonstration site built with Atlas?
Kommentaar kasutajalt TomH 18. juuni 2025, kell 08:05
I don’t think so - as far as I know there’s nothing at the moment other than a proposal to try and get people to give them money to recruit a whole team of people to build something.
Hopefully any potential funders will ask how likely any result is to be used before they agree to send them a whole load of cash.
Kommentaar kasutajalt dieterdreist 18. juuni 2025, kell 08:35
Openness
Our goal is to replicate the core philosophy of OSM, being open and collaborative. You can contribute to both design and development. Currently, we are using Figma as our design tool, but we plan to release a version compatible with Penpot to make collaboration even more accessible to different contributors.
I don’t understand how you could have chosen Figma as the design tool if openness is a goal. It means you can only edit the files (proprietary format) “in the cloud” and must use their online system for saving (complete vendor lock-in).
Kommentaar kasutajalt Gustavo22Soares 18. juuni 2025, kell 11:20
@Dieterdreist We started using Penpot. but at the time it didn’t support design tokens. We’re waiting for the support for component variants to return to Penpot
Kommentaar kasutajalt -karlos- 18. juuni 2025, kell 14:47
The German project intents to not using any web-framework. They will use Mapilary. We should have a OSM Wiki page to compare the 3 (or more?) projects.
Kommentaar kasutajalt dpschep 19. juuni 2025, kell 14:43
Will this design system also cover cartographic design?
Kommentaar kasutajalt -karlos- 19. juuni 2025, kell 19:24
@dpschep You may read and ask about the German project here: https://community.openstreetmap.org/t/relaunch-openstreetmap-de/119539
Kommentaar kasutajalt Koreller 19. juuni 2025, kell 20:54
Very good news, good luck for this important project !
Kommentaar kasutajalt Gustavo22Soares 19. juuni 2025, kell 22:07
@dpschep For now we are making the more basic components, but since it is aimed at OSM, yes.
@koreller Thanks
Kommentaar kasutajalt atdt 19. juuni 2025, kell 22:57
Nice work! I noticed the credit to Wikimedia Codex at the end of the post. As a supporter of both the OpenStreetMap and Wikimedia, it’s great to see this kind of cross-pollination of ideas and resources. It would have been fantastic to acknowledge this a little more prominently. I would have loved to hear at least a brief mention of how it inspired you and what elements of it you intend to remix or reuse. That would be a great way to show appreciation and foster goodwill and potential collaboration.
Kommentaar kasutajalt Gustavo22Soares 20. juuni 2025, kell 00:52
@atdt Thank you, I wish I had known Codex earlier, it was very important for us to get to where we are now. But to summarize, we used the color token naming conventions and the project documentation, as well as the organizational structure, like ADRs, issue templates, and documentation models. I can write later to talk more about the process and go into detail about the inspirations from Codex. Codex is amazing design system
Kommentaar kasutajalt aliensuperstar 1. juuli 2025, kell 05:14
Booooo! Inter again!