* ✨ Explain why a library cannot be disconnected in its modal A library that another connected library uses cannot be disconnected from a file, but the Libraries modal showed it with the same disconnect button as any other library, only disabled, and said nothing about why. Replace that button with an icon and a tooltip. A nested library ("Connected through ...") says it is inherited from its parent, and a direct library that another connected library uses says which one. Both name the library to disconnect first. A library nothing else uses keeps its button. library-disconnect-hint decides the case from the same data the disabled state used, so the buttons that were disabled are the ones that change. The legacy libraries tab keeps its button. Closes #12838 AI-assisted-by: claude-opus-5-5 AI-assisted-by: claude-sonnet-5-5 Signed-off-by: Filip Sajdak <filip.sajdak@siili.com> * 🐛 Name every library to disconnect in the disconnect hint The hint named only the parent of a nested library as the one to disconnect. That was wrong when several libraries use it (disconnecting one leaves it linked through the others) and no help when the parent is nested too and has no disconnect button either. The removal step now lists the libraries the user can actually disconnect: those that use the library directly or through others, and that no linked library uses. The parent is still named as the reason it is inherited. In a cycle nothing is removable, so the parent is named as before. Tests cover a shared dependency, a deep chain and a cycle. AI-assisted-by: claude-opus-5-5 AI-assisted-by: claude-sonnet-5-5 Signed-off-by: Filip Sajdak <filip.sajdak@siili.com> * 🐛 List directly linked libraries in the disconnect hint A library linked to the file directly stays until the user disconnects it, even when another linked library uses it. The hint skipped those: for a file linked to A and B, with A using B and B using C, it told the user to disconnect only A, and C stayed linked through B. Collect the libraries that use it, however far up, and that are either linked directly or used by no linked library. A directly linked library that another one uses cannot be disconnected yet, and its own tooltip says to disconnect that one first. The test covers a directly linked intermediate library. AI-assisted-by: claude-opus-5-5 AI-assisted-by: claude-sonnet-5-5 Signed-off-by: Filip Sajdak <filip.sajdak@siili.com> * 🐛 Count a library linked in this session as direct in the hint Only the libraries fetched when the workspace opens carry :is-indirect. One linked afterwards comes back without it, so the hint did not treat it as directly linked: after connecting B (which uses C) and then A (which uses B) without reloading, C's tooltip said to disconnect only A, and C stayed linked through B. A library the user linked has no flag and is direct by construction, so only one known to be indirect is skipped. The test covers that sequence. AI-assisted-by: claude-opus-5-5 AI-assisted-by: claude-sonnet-5-5 Signed-off-by: Filip Sajdak <filip.sajdak@siili.com> * 🐛 Flag libraries linked in this session as direct or indirect Only the libraries fetched when the workspace opens carried :is-indirect. Linking a library afterwards loads it and its dependencies through load-library-file, and none of them got the flag, so a missing flag could mean either. The disconnect hint in the Libraries modal reads it to tell which libraries the user can disconnect, and it listed the wrong ones for a chain connected in the same session (it named a dependency that has no disconnect button). Set the flag where the library is loaded: the library the user links is direct and the libraries it brings in are indirect. The hint is back to trusting only a flag that says false, because a missing one no longer means a direct link. The test links a library with one dependency and checks both flags. AI-assisted-by: claude-opus-5-5 AI-assisted-by: claude-sonnet-5-5 Signed-off-by: Filip Sajdak <filip.sajdak@siili.com> * 🐛 Keep a library's direct flag when it is loaded twice When links overlap, a library can be requested twice: once because the user linked it and once because a library linked right after brings it in. Each load stored its own :is-indirect value, so whichever answer landed last won, and an indirect one could erase the direct link. The disconnect hint then listed the wrong libraries. Store a loaded library through one event that never turns a known direct link into an indirect one. The reverse order already ends direct, since the user's link is stored with the flag false. The test links a library and then one that uses it before the first answer arrives, and answers in the order that used to lose the flag. AI-assisted-by: claude-opus-5-5 AI-assisted-by: claude-sonnet-5-5 Signed-off-by: Filip Sajdak <filip.sajdak@siili.com> * 🐛 Scope a library's kept direct flag to the file it belongs to The flag kept when a library is loaded twice was read from :files, which outlives a workspace. A library that was a direct link of the file visited before could keep that flag in the next file, where another library only brings it in, and the disconnect hint then listed one library too many. Keep the flag only when it was recorded for the file being loaded, using the :library-of the entry already carries. The test leaves a library flagged direct for another file and links a library that brings it in. AI-assisted-by: claude-opus-5-5 AI-assisted-by: claude-sonnet-5-5 Signed-off-by: Filip Sajdak <filip.sajdak@siili.com> * 💄 Name the libraries in the disconnect hint as design asked The nested library hint now reads "Connected through <parent>. To remove it, disconnect <libraries>." instead of "Inherited from ...". The library names in both hints (connected through and used by) show in the primary foreground color, so they stand out from the text. The translation is split on its two placeholders instead of rendered as HTML, because the library names are written by users. The full plain sentence stays as the aria label of the icon. The new key is workspace.libraries.connected-through-hint, since workspace.libraries.connected-through already labels the parent in the list. AI-assisted-by: claude-sonnet-5-5 Signed-off-by: Filip Sajdak <filip.sajdak@siili.com> --------- Signed-off-by: Filip Sajdak <filip.sajdak@siili.com> Co-authored-by: Eva Marco <evamarcod@gmail.com>
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