Get Involved/design: Difference between revisions
Move table of communication-related links into the "Communication and workflow" section and delete the now-empty "Join the VDG!" section |
Merge the information in the "Recent Changes" and "Current Projects" sections because they're saying the same thing; remove unhelpful or redundant information; move links into the text where they are more relevant |
||
| Line 9: | Line 9: | ||
First read through [[Get Involved/Design/Lessons Learned]]. This page contains often-talked design ideas and how the VDG understands them. This page can give context to some of the discussions happening in our live channels. | First read through [[Get Involved/Design/Lessons Learned]]. This page contains often-talked design ideas and how the VDG understands them. This page can give context to some of the discussions happening in our live channels. | ||
== | == Current Projects == | ||
Our default "Breeze" visual style is undergoing many changes as part of the [https://phabricator.kde.org/T10891 "Breeze Evolution" project]. If you would like to submit mockups for our consideration, use the new [https://www.figma.com/file/gjuIy1rxU9xHkaJXM0pasK/ocean-v3?node-id=1336%3A7194 New Figmt-based Breeze SVG Kit] have the most updated graphics for your mockups. This helps our developers visualize your design ideas better. | |||
Beyond that, here are some timeless ways to get involved in ongoing work: | |||
* Learn how to design Breeze icons by reading [https://develop.kde.org/hig/style/icons/ the applicable HIG page], and then work on [https://bugs.kde.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&component=Icons&list_id=1536878&product=Breeze&query_format=advanced Breeze icon bugs]. Here's [[Guidelines and HOWTOs/Submit an icon | how to submit an icon]]. | * Learn how to design Breeze icons by reading [https://develop.kde.org/hig/style/icons/ the applicable HIG page], and then work on [https://bugs.kde.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&component=Icons&list_id=1536878&product=Breeze&query_format=advanced Breeze icon bugs]. Here's [[Guidelines and HOWTOs/Submit an icon | how to submit an icon]]. | ||
* Submit patches (using [https://invent.kde.org/websites/hig-kde-org/merge_requests GitLab]) for corrections and improvements to the [https://develop.kde.org/hig/ Human Interface Guidelines] | * Submit patches (using [https://invent.kde.org/websites/hig-kde-org/merge_requests GitLab]) for corrections and improvements to the [https://develop.kde.org/hig/ Human Interface Guidelines] | ||
== Communication and Workflow == | == Communication and Workflow == | ||
{{Note|VDG task and project-tracking was done on [https://phabricator.kde.org/tag/vdg/ Phabricator] in the past, but is now moving to GitLab. [https://invent.kde.org/teams/vdg/issues/-/issues/new Click here to start a new discussion on GitLab]}} | |||
Most VDG discussions start out informally in real-time chat, accessed using [https://app.element.io/#/room/#visualdesigngroup:kde.org Matrix] or [https://t.me/vdgmainroom Telegram] (your choice, but Matrix is preferred). Once there is general agreement in the real-time chat, the discussion moves to a GitLab task. Our goal is to open the discussion to include developers, and make the proposal more concrete using images and mockups. | |||
Make sure to tag all the relevant participants in a [https://invent.kde.org/teams/vdg/issues/-/issues GitLab issue] discussion. Summarize the discussion and initial VDG conclusion when writing the task's initial description. Include before/after images of the proposed change. Explain the benefits for the user and possible red flags. | |||
In the GitLab task, it's common for details and scope to change based on developer feedback. This is normal! Developers may have a better idea of what is technically possible or reasonable to change given our constraints. Listen to developer feedback and change your design accordingly. At the same time, encourage them to listen to your expertise, and provide good evidence of your decisions as varying views will challenge your proposal. | |||
Once there's general agreement in the GitLab task, work should begin and folks can start submitting patches! | |||
! | |||
It can also be helpful to subscribe to the [https://mail.kde.org/mailman/listinfo/visual-design VDG mailing list] to keep abreast of general information relevant to all VDG contributors. This is a very low-traffic mailing list so you will not be spammed with nonsense. | |||
== Know Yourself == | == Know Yourself == | ||
| Line 53: | Line 39: | ||
* [[Guidelines and HOWTOs/Submit an icon | How to submit changes to an icon or submit a new icon]] | * [[Guidelines and HOWTOs/Submit an icon | How to submit changes to an icon or submit a new icon]] | ||
* [[Guidelines and HOWTOs/Icon Workflow Tips| Icon workflow tips]] | * [[Guidelines and HOWTOs/Icon Workflow Tips| Icon workflow tips]] | ||
== Old Things == | == Old Things == | ||
* [[KDE_Visual_Design_Group/Archive | Archive of outdated documents that may still be useful for reference]] | * [[KDE_Visual_Design_Group/Archive | Archive of outdated documents that may still be useful for reference]] | ||
Revision as of 20:34, 1 November 2021
About the Visual Design Group (VDG)
The Visual Design Group is a team dedicated to bettering the entire user experience of KDE software, including human interface design, graphical design, user interface design and interaction design. The aim is to help KDE create software that is both beautiful and a pleasure to use.
The VDG welcomes people with skills in art, visual design, and human-computer interaction--or even just an interest in elegant design! If you have good ideas about how software should look and behave, you are a designer too, and we'd love for you to join in. Our group regularly interfaces with users, developers, and the Promo Team.
The VDG created and maintains the KDE Human Interface Guidelines and the Breeze theme used throughout KDE Plasma and applications.
First read through Get Involved/Design/Lessons Learned. This page contains often-talked design ideas and how the VDG understands them. This page can give context to some of the discussions happening in our live channels.
Current Projects
Our default "Breeze" visual style is undergoing many changes as part of the "Breeze Evolution" project. If you would like to submit mockups for our consideration, use the new New Figmt-based Breeze SVG Kit have the most updated graphics for your mockups. This helps our developers visualize your design ideas better.
Beyond that, here are some timeless ways to get involved in ongoing work:
- Learn how to design Breeze icons by reading the applicable HIG page, and then work on Breeze icon bugs. Here's how to submit an icon.
- Submit patches (using GitLab) for corrections and improvements to the Human Interface Guidelines
Communication and Workflow
Note
Most VDG discussions start out informally in real-time chat, accessed using Matrix or Telegram (your choice, but Matrix is preferred). Once there is general agreement in the real-time chat, the discussion moves to a GitLab task. Our goal is to open the discussion to include developers, and make the proposal more concrete using images and mockups.
Make sure to tag all the relevant participants in a GitLab issue discussion. Summarize the discussion and initial VDG conclusion when writing the task's initial description. Include before/after images of the proposed change. Explain the benefits for the user and possible red flags.
In the GitLab task, it's common for details and scope to change based on developer feedback. This is normal! Developers may have a better idea of what is technically possible or reasonable to change given our constraints. Listen to developer feedback and change your design accordingly. At the same time, encourage them to listen to your expertise, and provide good evidence of your decisions as varying views will challenge your proposal.
Once there's general agreement in the GitLab task, work should begin and folks can start submitting patches!
It can also be helpful to subscribe to the VDG mailing list to keep abreast of general information relevant to all VDG contributors. This is a very low-traffic mailing list so you will not be spammed with nonsense.
Know Yourself
In a highly technical field like programming, it's easy to ecnounter the limits of your expertise. This is more difficult in subjective fields like art and design, and it's very important to have a firm grasp of what you can do. For example:
- If you know you're not very artistically skilled, listen attentively to developers and experienced designers on what we look for.
- Request honest feedback for your design proposals regarding what could be improved rather than blindly pushing on them.
- If you want to learn more about human-computer interaction, offer to help in testing interactions and providing feedback.
- How to change the default wallpaper
- How to submit changes to an icon or submit a new icon
- Icon workflow tips