* ♻️ Merge duplicated e2e loads and harden ten spec groups Collapse multi-case Playwright specs into one test with a named step per case, so the app or document loads once per group instead of once per case. No case is dropped. In scope, the affected cases fall from 85 to 52 tests and from about 1300 to 760 worker-seconds. - stroke-to-path and toolbar (15 to 2 tests, -80%): each step anchors a layer row to its exact name, checks the count grows by one and that the clicked row is selected before the context menu. The skipped path case now uses the tool's click-per-node and Enter gesture. The curve step counts exact Path rows; the update-file override that returned a whole file is gone; the toolbar test runs on the DOM renderer because the prebuilt WASM bundle creates no text. - dimension tokens and colorpicker (12 to 6, -45%): steps assert the resolved pill value, not just the pill; the width/height step detaches the extra pill. HSB now awaits isVisible on real labels, gradient steps count stops and the radial case switches its own type. - export frames and multiselection (11 to 3, -70%): rows use aria-checked instead of a 500 ms sleep, and steps wait for the sidebar before editing so a stale render cannot write to the previous selection. The frames entry is checked by row count and the "file" item by id. - variants and workspace (41 to 37, -29%): waits now follow rendered state, the duplicated setupEmptyFile is gone, and the layer tree derives its children container from the row's own id. The copy/paste flake is fixed with a selectRow retry, Escape to deselect, hover instead of clicks and idempotent container expansion. - grid editor and sidebar scroll (6 to 4, -24%): the editor opens once and blind 200/500 ms waits are gone; hover checks computed opacity because the button is hidden with opacity: 0. Only the second scroll test stays; the store has nine unit tests in ui/sidebar_scroll_test.cljs. Also drop a dead binding, restore two Taiga links and fix comments that cited the wrong drawing.cljs ranges and cancel-drawing's docstring. AI-assisted-by: deepseek-v4.1-flash * ♻️ Close the e2e merge review findings Restore the renderer coverage the merge lost and make the merged steps measure their own work. The five shape tools run under WASM again, and the text tool runs there too with the v2 editor flag: WasmWorkspacePage already enables it, so the toolbar gesture keeps its drag and typing assertions. Curve now compares the exact Path rows with their own baseline. WorkspacePage gains layerRows, and layerRow delegates to it; toolbar, stroke-to-path and export-frames use them instead of local copies. The variants setup waits for the component icon and the variant rows instead of two fixed sleeps, selectRow clicks once, and the cut/paste step asserts its own delta. The stale comments lose their line numbers, Path is no longer called the pencil, the orphan fixture is deleted, and the sidebar smoke regains the Assets round trip. Document the local e2e bundle prerequisite in the frontend testing memory. Closes #13093 AI-assisted-by: deepseek-v4.1-flash * 🐛 Wait for the layer selection in the token spec The dimension-token test clicked a layer row and went back to the Tokens tab without proving the selection. A lost click left the previous shape selected, and the border-radius step could pass on that shape. The selection now goes through WorkspacePage.selectRow, which clicks once and waits for aria-checked. selectRow moves from variants.spec.js into the page object, and selectLayer delegates to it, so the click-and-wait selection lives in one place. 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