Based on our record, Pijul should be more popular than Zeplin. It has been mentiond 44 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
Using theory of patches would better compliment the current approach. Integrating a scm such as https://pijul.org or atleast the underlying tech would allow for better conflict resolutions. Transferring patches should also allow for more efficient use of io. - Source: Hacker News / 5 days ago
IMO Open Source software communities are where folks like you can really thrive. They're much closer at something like a meritocracy than traditional workplaces. > I want to make the next-gen version control system While you certainly could invent one yourself, you could consider contributing to popular ones like git/mercurial. It'd help teach you both the positive and the negative aspects of their design... - Source: Hacker News / 21 days ago
The feature I think I would most like to see is support for patches as a more first-class object. For example reverts and cherry picks have no real metadata. This leads to conflicts when merging branches that have cherry picks (although they often auto-resolve if they are exactly the same diff) and makes asking "Does $branch contain $patch" basically impossible to answer. https://pijul.org/ greatly improves this... - Source: Hacker News / about 1 month ago
In Pijul, conflicts are not modelled as a "failure to merge", but rather as the standard case. Specifically, conflicts happen between two changes, and are solved by one change. The resolution change solves the conflict between the same two changes, no matter if other changes have been made concurrently. Once solved, conflicts never come back. - from https://pijul.org/. - Source: Hacker News / 4 months ago
Do not try and bend the spoon, that's impossible. Instead, only try to realize the truth...there is no spoon. Then you will see it is not the spoon that bends, it is only yourself -- what Pijul users say when they overhear git users arguing with each other about monorepos. https://pijul.org/. - Source: Hacker News / 4 months ago
Additionally, thank you to all our community launch partners across the frontend ecosystem for helping us bring Storybook 8 to the world! Thanks to Chromatic, Figma, ViteConf, Omlet, DivRiots, story.to.design, StackBlitz, UXpin, Nx, Mock Service Worker, Anima, Zeplin, zeroheight, kickstartDS, and Kendo UI. - Source: dev.to / 4 months ago
Designers would often use separate tools like Zeplin or Invision to handoff the designs to developers.🚮. - Source: dev.to / 4 months ago
Zeplin — Designer and developer collaboration platform. Show designs, assets, and style guides. Free for one project. - Source: dev.to / 5 months ago
I'd suggest if you're going to use a tool to collaborate on finalized designs. One that doesn't rely on which design tool you use, why not use zeplin.io? There are free plans and paid plans, and it was purpose built for design delivery. Over 5 million users--over 3 million developers using it. Source: 12 months ago
It seems to be you and your team could benefit from a tool like zeplin. Source: about 1 year ago
Mercurial SCM - Mercurial is a free, distributed source control management tool.
Invision - Prototyping and collaboration for design teams
Git - Git is a free and open source version control system designed to handle everything from small to very large projects with speed and efficiency. It is easy to learn and lightweight with lighting fast performance that outclasses competitors.
Figma - Team-based interface design, Figma lets you collaborate on designs in real time.
GitHub Desktop - GitHub Desktop is a seamless way to contribute to projects on GitHub and GitHub Enterprise.
Balsamiq - Balsamiq. Rapid, effective and fun wireframing software.