Skip to content
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

Pi-ui Figma master file - Components and examples #323

Open
ta-lind opened this issue Mar 3, 2021 · 0 comments
Open

Pi-ui Figma master file - Components and examples #323

ta-lind opened this issue Mar 3, 2021 · 0 comments

Comments

@ta-lind
Copy link
Member

ta-lind commented Mar 3, 2021

@MariaPleshkova @amassarwi @tiagoalvesdulce

Over the past months we've transferred all the design work into Figma. The master file can be found here: https://www.figma.com/file/EanUbqJmPs8EMqY26j9zwo/decred-piui-master?node-id=12%3A0

If anyone wants to be added as viewer / editor, let me know on Matrix.

On the top left corner can find the different pages that are used to organize the work. Relevant ones for reference are:

Screenshot 2021-03-03 at 19 15 03

Decrediton - Latest

  • This contains key view examples with up to date components, and also latest design updates. Ideally aiming to be kept in sync with the release, as well lightweight by dropping older iterations into Archives. Reference point for views as whole.

Politeia - Latest (TBA)

Components, Type and Color

  • Individual components and their states. Kept in sync with pi-ui release. Ideally this is the source of truth or blueprint per each individual component.

Assets – Icons, Symbols

  • Icon, symbols and assets – presently being organized.*

Archive - Decrediton
Archive - Politeia

  • Bulk of the past iterations for both Decrediton and Politeia. May be useful to refer to how something works, but not how something should exactly look like.

Concepting - LN UX
Concepting - Trezor

"Conepting -" Contains low and mid quality drafts for concepts that still need validation. Avoid using as component and style reference.

To follow up with this, we should establish a process for components in the build to be synced up with the design and crunch out fixes to components which may be outdated or have issues. and crunch out fixes to components which may be outdated or have issues. I see one of the key issues here is that there's a lot of people doing contributions on front-end, thus it's easy to get a bunch of different translations of something.

Maria's setup a simple notion board, which may be used for example to keep track of status of components: https://www.notion.so/150d8fa08d8c4f199e7b31a4006e6543?v=ef9ec4692b944b39948e2956a5c57553, or alternatively we can use just issues in this repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant