A system of versioning like GitHub or Abstract

BrunoRosa

Hi everyone, i'm Bruno, a UX designer at PagSeguro PagBank in Brazil, with a focus in design system. I created this discussion because i'm working with zero height here in my company and seeing that not having a more complex versioning system makes things very difficult. The developers don't like zero height, and we would love to make it our primary and only source of truth. So I am creating this discussion.

Ragnar

Hi @BrunoRosa Thanks for the feedback! Could you tell me what specifically you're missing from the current releases feature? Just so we understand your needs a bit better.

chipcarroll

Ragnar I just wanted to add in as a new Zeroheight user, that i would love to see these proposed suggestions from everyone.

While versioning is great and what is there is better than nothing. At a large organization like where i work, we are working on the next major version of our Design System in tandem with the current version of the system. So for us to plan out these changes to documentation will require some fancy work and reminders.

Would be great to work off the current version, create a branch and then merge it back in all while having other branches being worked on and merged back in when they are ready.

AdamHay

I'm not sure if this is what was being proposed, but my team has a need to edit multiple versions of the documentation at one time. It would be very useful to have the ability to concurrently work on a 'bug fix' or 'minor update' version while also being able to build out a 'next major release' version. if we start adding new major release items to the "Latest" version, we no longer have the ability to bug fix the current version without polluting it with these major release items. in a perfect world we would be able to create multiple versions, then switch the "Latest" or WIP designation to any of the existing release versions, much like you can with the Default designation.

snds-zuora-117

AdamHay It would also be good to be able to merge deltas of changes being made by a team.

BenZayed

snds-zuora-117

snds-zuora-117 if components are tagged/labeled and fell into sort of categorization this could be easily happen with either (Checkbox items for small projects) or with Tag for (Core, Current, Extended, Next) Version labled on each component needed.

So all we need is just choose All Extended and Next edited components as packages to creat (New Version for Instant Reviewing and testing)
While Core items/components need to get its Own Checkbox to say which is getting updates and when each is approved and added it generates new Core Version of the core components that shapes our service/product Usability!

LarryReynolds

+1 all of this. Also, an option for taging/labeling individual component versions would be very helpful, as well as being able to surface the latest version in the component grid or page (instead of just in the inspect take-over.) Even better, add some sort of change-log module for component pages.

RSB

+1 for us too! The current way the releases work seems backwards. There are well established version control strategies (lGit) that are used for development, and the main concepts should added here.