Minor collaboration, design review, social media revisions #610
Conversation
Refreshing the copy to be more up-to-date, along with some typo fixes, and text tweaks.
Replacing the channel link with an invite link (for those who aren't members yet).
mouxdesign
left a comment
mouxdesign
left a comment
There was a problem hiding this comment.
Added some minor copy tweaks and brought in the research aspect as well. Not sure if it might be useful to include the research calls here or to create a separate section altogether on the research calls and how they can support projects.
| This is not meant to be a strict rule set. Every project is unique, and healthy collaboration requires everyone involved to be sensitive to the projects needs and goals. Our own goal is to support projects and contributors to improve their products and design practices (and not impose our ideas). | ||
| This is not meant to be a strict rule set. Every project is unique, and healthy collaboration requires everyone involved to be sensitive to the projects needs and goals. Our own goal is to support projects and contributors to improve their products and design practices (and not impose our ideas). | ||
|
|
||
| Here are six types of design needs a project may have. |
There was a problem hiding this comment.
| Here are six types of design needs a project may have. | |
| Here are seven types of ways a project can engage and collaborate with the community: |
There was a problem hiding this comment.
Where does the seventh one come from? The page headers only go to #6.
| 1. Engage in Discord conversations to share ideas and get feedback | ||
| 1. Participate in a design review session | ||
| 1. Participate in a [design review session](Design-Reviews.md) | ||
|
|
There was a problem hiding this comment.
- Participate in a UX research review session
There was a problem hiding this comment.
Do we have something more official on UX review sessions? Can we also accommodate those in the design reviews to avoid having similar types of sessions?
Design-Reviews.md
Outdated
| ## How does it work? | ||
|
|
||
| 1. A bitcoin product team submits a page or section they want reviewed in a design reivew in the [#design-reviews](https://discord.gg/ss2ZbNcv32) channel in our Discord. | ||
| 1. A bitcoin product team submits a page or section they want reviewed in a design review in the [#design-reviews](https://discord.gg/ss2ZbNcv32) channel in our Discord. |
There was a problem hiding this comment.
- A bitcoin product or team submits a goal that they have interms of understanding a particular set of user problems or user persona.
|
Added a review and brought a bit of the research angle into the content as well. |
Co-authored-by: Mogashni <90313394+mouxdesign@users.noreply.github.com>
3 participants
Refreshing the copy to be more up-to-date, along with some typo fixes, and text tweaks.
A separate topic maybe, but I am wondering how many people actually read the markdown content in this repo, and if the website is not a better place for most of it. The Domains.md file should probably remain here because it's more of a governance contract, but the other content is probably easier to find via the site. What do you think?
Closes #601