8b9558b380
* ✨ Add unit tests for the token name schema Cover make-token-name-schema, the schema that rejects a token name whose path clashes with an existing token or group. The lower-level token-name-path-exists? already had a test; the schema that composes it did not. The cases pin an exact duplicate, a token inside a token, a token name that collides with a group, an existing child path, valid siblings, the fail-closed nil tree, invalid syntax and the length limit. This is the unit-test base for reducing the 15 group-name-clash e2e cases to two. AI-assisted-by: deepseek-v4.1-flash * ♻️ Remove duplicate token tests and fix the spread step The three top-level tests duplicated the ones inside the creation describe; only the indentation differed. Keep the originals. The shadow token test labelled "Valid spread" filled the blur field, so the token under test ended with blur 0 and the spread never changed. Fill spread instead and expect the referenced token to resolve with Blur: 4. AI-assisted-by: deepseek-v4.1-flash * ♻️ Reduce the token group-name-clash e2e matrix to two tests The fifteen cases repeated the same setup and only changed the token type and value. The rule is now covered by the token name schema unit test, so keep two representatives: thirteen simple types in one test with a test.step each, and the two composite forms (Typography and Shadow) in a second test. The helper no longer re-runs the file setup, so each test loads the page once: 15 page loads become 2 and the block drops from 433 s to about 21 s. AI-assisted-by: deepseek-v4.1-flash * ♻️ Cover the numeric token creation types in one test The nine creation tests repeated the same validation ladder and only changed the token label and placeholder. Run the ladder once in the border radius step, keep the reference token creation, and create the other eight types with a test.step each. The new helpers split the flow: open the form, assert the ladder, save a token. The e2e drops from nine page loads to one. AI-assisted-by: deepseek-v4.1-flash * ♻️ Reduce the remapping e2e spec to three tests Keep one remapping flow per token shape: box shadow with alias references, border radius with a value change, and a group rename with undo. The two cancel paths lose their own page loads and become steps inside the shadow test: close keeps the original name, and "don't remap" renames the token and breaks the reference. The deleted typography and shadow applied-shape cases exercise the same data path, which the remapping unit tests already cover. AI-assisted-by: deepseek-v4.1-flash * ♻️ Shrink the tooltip and numeric-revert e2e tests The tooltip test asserted five message shapes over eleven layer selections. Keep the three that have no unit test: a deleted token, a reference outside the active sets, and a token in an inactive set. Each is one step with a pill label and its tooltip text. Three of its five messages were already covered by the token pill unit test, including both resolved-value cases. Keep one numeric-revert test and drop the fixed sleeps: await the value with toHaveValue instead. Division by zero and the min/max clamp are unit-tested in the numeric input tests. AI-assisted-by: deepseek-v4.1-flash
Website • User Guide • Learning Center • Community
Youtube • Peertube • Linkedin • Instagram • Mastodon • Bluesky • X
Penpot is the open-source design platform for teams that build digital products at scale.
Penpot’s key strength lies in giving you full ownership of your design infrastructure. Built on open source and designed for self-hosting, it puts teams in complete control of their design environment supporting strict compliance and governance requirements. Whether used in the browser or deployed on your own servers, Penpot works with open standards like SVG, CSS, HTML, and JSON.
Real-time collaboration strengthens this foundation, helping teams scale and bring design closer to the product through top-tier capabilities. Additionally, developers feel at home using Penpot, because design is expressed as code, enabling a direct translation and shipping products faster.
Best-in-class native Design Tokens provide a single source of truth between design and development. They ensure consistency, improve collaboration, and make it easier to manage complex design systems.
The MCP server takes it further by enabling multi-directional workflows between design and code. A powerful open API and plugin system makes the workspace programmable, enabling automation, AI-driven workflows, and integrations with the tools and systems you already use.
With CSS Grid and Flex Layout, teams can design responsive interfaces that behave like real code from the start.
Combined, these features turn Penpot into a full-stack design platform for building scalable design systems and fully integrated product development processes.
If your organization is scaling and needs extra support, we’re here to help. Talk to us
Table of contents
Why Penpot
Penpot connects design, code, and AI workflows through a code-based approach, making designs readable by developers and AI via the MCP server. This approach helps teams ship what’s actually designed and manage design systems at scale with powerful design tokens. As a self-hosted, open-source and real-time collaboration platform, Penpot offers full flexibility, security, and ownership without vendor lock-in. Learn more about why Penpot is the platform for your team.
Plugin system
Penpot plugins let you expand the platform's capabilities, give you the flexibility to integrate it with other apps, and design custom solutions.
Designed for developers
Penpot was built to serve both designers and developers and create a fluid design-code process. You have the choice to enjoy real-time collaboration or play "solo".
Inspect mode
Work with ready-to-use code and make your workflow easy and fast. The inspect tab gives instant access to SVG, CSS and HTML code.
Integrations
Penpot offers integration into the development toolchain, thanks to its support for webhooks and an API accessible through access tokens.
Building Design Systems: design tokens, components and variants
Penpot brings design systems to code-minded teams: a single source of truth with native Design Tokens, Components, and Variants for scalable, reusable, and consistent UI across projects and platforms.
Getting started
Penpot is the only design & prototype platform that is deployment agnostic. You can use it in our SAAS or deploy it anywhere.
Learn how to install it with Docker, Kubernetes, Elestio or other options on our website.
Penpot Enterprise
Penpot Enterprise is our paid plan for organizations that need to scale their design work across multiple teams with advanced governance, security, and administration. Manage teams and access from a centralized Admin Console, configure advanced permissions, and connect your identity provider through SSO. Available for cloud and self-hosted environments, it combines enterprise controls with Penpot’s open-source foundation and open standards.
Community
We love the Open Source software community. Contributing is our passion and if it’s yours too, participate and improve Penpot. All your designs, code and ideas are welcome!
Want to go a step further? Become a Penpot Ambassador and help grow the Penpot community in your region while contributing to a global, open design ecosystem.
If you need help or have any questions; if you’d like to share your experience using Penpot or get inspired; if you’d rather meet our community of developers and designers, join our Community!
Categories include:
- Ask the Community
- Troubleshooting
- Help us Improve Penpot
- Events and Announcements
- Penpot in your language
- Education
Code of Conduct
Anyone who contributes to Penpot, whether through code, in the community, or at an event, must adhere to the code of conduct and foster a positive and safe environment.
Contributing
Any contribution will make a difference to improve Penpot. How can you get involved?
Choose your way:
- Create and share Libraries & Templates that will be helpful for the community.
- Invite your team to join.
- Give this repo a star and follow us on Social Media: Mastodon, Youtube, Instagram, Linkedin, Peertube, X and BlueSky.
- Participate in the Community space by asking and answering questions; reacting to others’ articles; opening your own conversations and following along on decisions affecting the project.
- Report bugs with our easy guide for bugs hunting or GitHub issues.
- Become a translator.
- Give feedback: Email us.
- Contribute to Penpot's code: Watch this video by Alejandro Alonso, CIO and developer at Penpot, where he gives us a hands-on demo of how to use Penpot’s repository and make changes in both front and back end.
To find (almost) everything you need to know on how to contribute to Penpot, refer to the contributing guide.
Resources
You can ask and answer questions, have open-ended conversations, and follow along on decisions affecting the project.
✏️ Tutorials
🏘️ Architecture
🧑🏫 UI Design Course
License
This Source Code Form is subject to the terms of the Mozilla Public
License, v. 2.0. If a copy of the MPL was not distributed with this
file, You can obtain one at http://mozilla.org/MPL/2.0/.
Copyright (c) KALEIDOS SUBSIDIARY SL
Penpot is a Kaleidos’ open source project