New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a page for design collaboration and shared design resources #35
Comments
Don't have any concrete feedback to add, except that I really like the idea of having all of these at a single page. Navigating through Figma is not always easy, so if it means anything, I find this kind of page quite helpful. |
@GBKS and I were discussing the dev-designer workflow around a specific issue we have on @btcpayserver so I documneted the typical process. Of course, in a fast-paced environment things don't always go in a pattern like this, but this is quite typical flow. BTCPay Dev/Designer collaboration on an issueThe goal of this document is to quickly describe the workflow of the designer and dev community when tackling a particular UX/UI related issue.
|
Ship it! |
Based on #35, with slight updates to copy and resources, as the original issue iis pretty old by now.
I think a page like this could help us with two things.
First, it looks like we will be using Figma for many designs due to the ease of sharing and collaboration. While Github has many pre-defined processes built-in, Figma and other design tools do not. So I think it would be helpful if we articulate these for us.
Second, there are a few design resources being worked on that we will make publicly available for anyone to use and contribute to. Currently we have many Figma links floating around with no way to find them again other than asking around or searching Slack/Figma history. We can also list important design resources on this page.
This page would likely be under "Resources".
Below is a mock-up with some quickly written copy. What do you think of this? Note that this is heavily slanted towards collaborating on Figma community files. So this might need to be a sub-page under a more general "Design collaboration" or "Open design" section that is tool-agnostic.
The text was updated successfully, but these errors were encountered: