Florian Schrödl 3c4ae62db5
⚡ Resolve tokens incrementally with tokenscript (#12437)
With the tokenscript flag every resolution rebuilt the whole library:
each sidebar render, each propagation and each keystroke in a token
form. The adapter now keeps the interpreter state of the last
resolutions and updates it with set-sets, so only the tokens that
changed and their dependents are re-resolved and converted. Every other
output token stays the same object.

- common/deps.edn moves penpot/tokenscript-interpreter to v0.3.0:
  token readers and writers and a set-sets that looks only into changed
  sets (#1), on top of the DTCG import and export (#4) Penpot already
  uses.
- The sidebar, token propagation, token application and the plugin API
  pass the active sets unmerged (cfo/get-active-token-sets and its
  force variant); the interpreter merges them. The plugin API's own
  resolution cache is gone.
- The adapter hands Penpot's token records to the interpreter with a
  reader (value and DTCG type, an error for a token without a value)
  and a writer (the conversion to :resolved-value or :errors), which
  runs only for the re-resolved names.
- The cache resolves new sets from the last resolution with the same
  set ids, else from one sharing a set id, else from scratch.
- The token form controls resolve the draft in a set of its own on top
  of the library's sets, the selected set last
  (cfo/get-token-sets-for-edit). The form leaves the edited token's old
  name out of them (cfo/without-token). A keystroke re-resolves only
  the draft and its dependents. The last draft is cached apart, so
  typing doesn't evict the sidebar's resolutions. Without the flag the
  controls don't build these sets. The plugin API's token name and
  value setters validate the candidate the same way.
- The token form hint shows resolved font families as a name list.
- Tests cover the unmerged set helpers, a plugin rename to a name below
  the old one (which needs the old name left out), and compare renames,
  with and without updating the references, against StyleDictionary.

Signed-off-by: Florian Schroedl <flo.schroedl@gmail.com>
2026-11-20 13:54:15 +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%