Plugin API (Empowering the community)

I understand that the team is currently busy with auto-layout and other highly-requested features. I’m curious where the plugin API falls on the priority list.

I imagine that at this stage the internal API itself is changing so often that having an external-facing API to maintain would be a huge headache. On the flipside, a plugin API would empower the community to build missing functionality and augment the current toolset.


Hi @lucadalli, I have answered this question and other recent FAQ here: Are you new to the Penpot community? That's how you can get started!

(spoiler: we are still exploring how to do it, but for sure it’s in our plans)