Video version:
This is a companion discussion topic for the original entry at https://anditosan.wordpress.com/2025/10/25/plasma-design-system-leaps-forward-with-migration-to-penpot/
Video version:
That’s so cool!
@Anditosan, can the absolute latest versions ever be publicly modifiable, like source code is? It’s certainly FOSS either way, but that seems like a shame.
At a basic level, these are just .json files. However, we have asked for ways that libraries could be synchronized. Git is probably not the best place since it can’t build a .penpot file for the library. So the only semi-workable solution is to send the library to PenPot for them to feature on their store or provide the file via git with incremental updates instead.
We understand that it’s an area they are interested in but that there is no option for it at the moment.
To enable worldwide collaboration, we are periodically exporting the Penpot file and uploading it to our GitLab repository (currently hosted in a personal repo, but moving to a Plasma-backed one soon). This means anyone can clone the repository and work with the same assets we do.
What does this workflow look like? If a person wants to work with the assets in KDE’s PenPot instance, how do they take this export and work with it?
Or can they work on the KDE PenPot instance directly?
Yes, exactly. Any user that can download the penpot file (AKA PenPot library) can load it up into their own PenPot instance, much like a fork in git. However, the file is not synchronized. We will have to keep pushing periodic updates and then git users would repeat the library loading process.
How do you get your own PenPot instance you can load the file into?
After you make changes to the .penpot file locally, how do you submit those changes for review and (hopefully) integration into the original version?
What happens if someone else makes changes to the original version while you were making your changes to your version? How do they get synced up again?