Andrey Antukh d6e816daa0
✨ Cover subscription rules with unit tests and trim e2e specs (#13006)
Move the pure subscription rules out of the browser specs and into unit
tests, then keep only the cases a browser can prove.

- Extract show-manage-subscription-link? and show-main-menu-power-up? from
  the dashboard team panel and the workspace main menu, and use them at
  both call sites. A new subscription_dashboard_test.cljs covers which
  plan a subscription reads to, including unpaid and canceled demotion, the
  owner and enterprise sides of both affordances, and the banner and
  members-CTA boundaries: four editors over the seats, no usage data, and
  the demoted plans.
- Add get-versions-stored-days tests to workspace_versions_test.cljs: an
  active nitrate or enterprise license keeps 90 days, a canceled one lets
  the team plan decide, a license without the admin console does not count,
  and unlimited, enterprise, professional and planless teams keep 30, 90
  and 7 days.
- Rewrite the profile usage tests as async tests with mock/with-mocks* and
  an async transport double: the editors from the usage call reach
  [:props :subscription :editors], a failing call leaves the profile
  untouched and logs once, and the call is skipped without the
  subscriptions flag.
- Cut the e2e suite from 13 cases to 7. Five dashboard cases keep the menu
  icon, the two sidebar plan names, the owner-only settings link and the
  members CTA; two workspace cases keep the translated days warning with
  the upsell step and the enterprise menu with no upsell. Assert the
  unlimited glyph and drop the CTA count.
- Drop the three get-team-info mocks the dashboard never calls and six
  unreferenced subscription fixtures, reusing the invitations fixture.
- Sort the subscription test requires in runner.cljs: cljfmt's
  :sort-ns-references? wants subscription-dashboard-test first.

Closes #13005

AI-assisted-by: deepseek-v4.1-flash
2026-11-20 13:45:59 +01:00
2026-11-20 11:59:29 +01:00
2026-11-19 12:12:02 +01:00
2021-11-15 09:54:36 -05:00
2026-11-20 09:53:37 +01:00
2026-11-20 09:53:37 +01:00
2020-08-11 10:11:23 +02:00
2026-11-12 11:02:34 +01:00
2025-01-22 15:46:23 +01:00
2026-07-22 14:18:51 +02:00
2017-03-06 18:42:58 +01:00
2026-11-16 10:58:05 +00:00
2025-06-02 12:09:20 +02:00
2023-11-15 10:55:39 +01:00
2026-11-19 08:25:50 +01:00
2026-06-09 18:48:03 +02:00

Verified DPG Penpot Community Managed with Taiga.io

Website • User Guide • Learning Center • Community

Youtube • Peertube • Linkedin • Instagram • Mastodon • Bluesky • X

Penpot video

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.

Penpot Design Systems

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.

2

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:

Pentpot Community

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:

To find (almost) everything you need to know on how to contribute to Penpot, refer to the contributing guide.

Penpot hub

Resources

You can ask and answer questions, have open-ended conversations, and follow along on decisions affecting the project.

💾 Documentation

🚀 Getting Started

✏️ Tutorials

🏘️ Architecture

📚 Dev Diaries

🧑‍🏫​ 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

Description
Penpot: The open-source design tool for design and code collaboration
Readme MPL-2.0 525 MiB
Languages
Clojure 75.6%
JavaScript 6.3%
Rust 6.2%
TypeScript 5.4%
SCSS 2.9%
Other 3.4%