Minor collaboration, design review, social media revisions (#610)

* Minor collaboration, design review, social media revisions

Refreshing the copy to be more up-to-date, along with some typo fixes, and text tweaks.

* Updating Discord link

Replacing the channel link with an invite link (for those who aren't members yet).

* Apply suggestions from code review

Co-authored-by: Mogashni  <[email protected]>

---------

Co-authored-by: Mogashni <[email protected]>

Collaboration.md

@@ -1,8 +1,8 @@
 # Bitcoin Design Community collaboration playbook
 
-The goal of this document is to define common types of collaborations, to serve as starting points for new inquiries. Collaborations should be tracked as issues with the "collabration" label, see the [current ones here](https://github.com/BitcoinDesign/Meta/issues?q=is%3Aopen+is%3Aissue+label%3Acollaboration).
+The goal of this document is to define common types of collaborations, to serve as starting points for new inquiries. Collaborations should be tracked as issues with the "collaboration" label, see the [current ones here](https://github.com/BitcoinDesign/Meta/issues?q=is%3Aopen+is%3Aissue+label%3Acollaboration). Many collaborations we have had so far are shown on the [projects page](https://bitcoin.design/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.
 
@@ -14,7 +14,7 @@ Ways the project can choose to interact with the community:
 
 1. Review the [guide](https://bitcoin.design/guide/) to find a direction or solution
 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)
 
 Our role in this scenario is to be a helpful partner in providing resources and feedback.
 
@@ -46,7 +46,7 @@ Solving single problems usually means to work within the current project framewo
 
 An existing project is maturing and wants to improve the overall design, which may also means finding a designer and adopting design processes.
 
-The term redesign is often used too quickly. Many times, it is better to systematically improve the existing design than start from scratch. This should be carefully considered.
+The term redesign is often used too quickly. Many times, it is better to systematically improve the existing design than starting from scratch. This should be carefully considered.
 
 Steps we can take:
 
@@ -70,6 +70,8 @@ Steps we can take:
 
 Designers who want to tackle redesigns should ensure they have the availability to regularly contribute for longer periods of time. How much time is required depends on the scope. In addition to designers, having a dedicated project manager available to help with planning and communication is also helpful.
 
+For longer collaborations with lots of good conversation, a dedicated Discord channel may be set up.
+
 ## #4 New project
 
 This is an opportunity to adopt a good design process from the start, beginning with researching product concepts, target audience research, etc. New projects likely also have other foundations to lay, so designers need to be flexible.

Design-Reviews.md

@@ -1,26 +1,34 @@
 # Bitcoin Design Reviews
 
-Design reviews are opportunities for bitcoin products to get design critiques on a particular feature or aspect of their product. Actionable suggestions for improving usability, user interface, interaction, and visual aesthetics are given by community members.
+Design reviews are opportunities for designers and product teams to get design feedback on a particular feature or aspect of their product as well as getting help in better understanding the needs of their users. Actionable suggestions for improving usability, user interface, interaction, and visual aesthetics are given by community members.
 
 ## 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 of the user flow they want reviewed in a design review in the [#design-reviews](https://discord.gg/ss2ZbNcv32) channel in our Discord.
 
-We will only focus on a specific part of your product, so we can give the highest amount of value. Reviewing a whole product is an extensive and involved process that is better suited to be dealt with by a dedicated product designer or a more involved process than a single call. If you need a designer for your bitcoin product, reach out in the [#opportunities](https://discord.gg/uBUHHkwTZe) channel.
+It is best to focus on a specific part of your product, so we can give the highest amount of value. Reviewing a whole product is an extensive and involved process that is hardly doable in a single call and better suited for a dedicated product designer or a more involved process. If you need a designer for your bitcoin product, reach out in the [#opportunities](https://discord.gg/uBUHHkwTZe) channel.
 
-2. The proposal is discussed by members of the community and a call is scheduled as appropriate.
+2. The proposal is discussed and a call is scheduled as needed.
 
-3. Designers interested in reviewing jump into a collaborative Figma file **PRIOR** to call, where they crit the product page or section submitted. This will all be public and open for anyone to view, in classic open-source fashion.
+3. The designer/team ideally shares their designs with an introduction several days in advance. This allows feedback gathering beforehand, participation for anyone who can't make the call, and makes the call more useful since everyone is already up-to-speed. This is public and open for anyone to view, in classic open-source fashion.
 
-4. Designers who review the product present their feedback to the product team in the scheduled call.
+4. What to consider during the call
 
-Follow up help and suggestions on the feedback given is always available. The product team and interested designers can independently organize this.
+4.1 Assume that not everyone has had a chance to review the product/design and provide a top-level summary. Then dive into the specific design to review.
+
+4.2 Do not expect final solutions to be created during calls. An hour is not enough time. You will get diverse feedback and can decide what to act on and what to dismiss based on your product direction.
+
+4.3 Allow designers who did their home work to present their feedback. It is often best to not interrupt, but only ask questions, and give explanations later.
+
+4.4 Ensure a good pace so you can hear all the feedback. Take notes, and if needed, follow up after the call for more details.
+
+5. Follow up help and suggestions on the feedback given is always available. The product team and interested designers can independently organize this.
 
 ## Who can take part?
 
 Anyone who is working on a bitcoin product. Whether its a new page or user flow you want reviewed before release, or an old one that needs polishing, Bitcoin Design Reviews can help. Open-source products get priority over closed-source products.
 
-Calls are recorded and published on the [BitcoinTV](https://bitcointv.com/a/bitcoin_design/videos) and [YouTube](https://www.youtube.com/@BitcoinDesign) channels, and open for anyone to join in. We greatly appreciate the pseudonymous and private nature of bitcoin and are more than happy to accommodate those who would prefer not to reveal their identity.
+Calls are recorded and published on the [BitcoinTV](https://bitcointv.com/a/bitcoin_design/videos) and [YouTube](https://www.youtube.com/playlist?list=PLpV0KfVOMojYDwQcdYt6anfQqqRk944Dq) channels, and open for anyone to join in. We greatly appreciate the pseudonymous and private nature of bitcoin and are more than happy to accommodate those who would prefer not to reveal their identity.
 
 ## What information do I need to provide for a review?
 

Social-Media-Guidelines.md

@@ -1,8 +1,15 @@
-# Social Media Guidelines
+# Social Media & Newsletter Guidelines
 
-## The [@bitcoin_design](https://twitter.com/bitcoin_design) Twitter account
+A public-facing version of this content can also be found on the website at [/social-media](https://bitcoin.design/social-media/). We also use the [#spread-the-word](https://discord.gg/PGz2r2UAmE) Discord channel to discuss these initiatives.
 
-The Twitter account gives more exposure to designers and efforts in the community. It also hosts the community call every 3 weeks via Twitter Spaces.
+## X/Twitter & Nostr
+
+Generally, We use social media as a point of contact and to share activity in the community more broadly. 
+
+We use:
+
+- [@bitcoin_design](https://twitter.com/bitcoin_design) on X/Twitter
+- [_@bitcoin.design](https://nosta.me/[email protected]) on Nostr
 
 ### Format
 
@@ -14,20 +21,20 @@ Voice, tone & writing style:
 - High signal-to-noise ratio
 - Friendly & approachable
 - Succinct
-- Use threads with each tweet capturing one idea/point
+- Use threads with each post capturing one idea/point
 
 Content ideas:
 
-- Guide highlights: When new content is added to the guide, create a new thread on the additions (or re-tweet the authors threads - probably better). 
+- Guide highlights: When new content is added to the guide, create a new thread on the additions (or repost the authors threads - probably better). 
 - Designer spotlight: highlight a designer in the community and share a short story about them / why they like bitcoin / what they work on etc.
 - Announce calls and call recordings (learning bitcoin & design, design review, community call…)
 - Quick user research and polls for community projects
 - Respond to current design-related conversations (e.g. post a link to the Units & Symbols page if there’s a thread somewhere around unit formatting)
-- Add context to tweets when RT'ing to add value
+- Add context to posts when RT'ing to add value
 
 Do:
 
-- OK to highlight when products, services, and brands adopt strategies from the Guide, or do things that’s good for open source bitcoin or open design processes
+- OK to highlight when products, services, and brands adopt strategies from the Guide, or do things that’s good for open-source bitcoin or open-design processes
 
 Don't:
 
@@ -50,7 +57,7 @@ Bad:
 
 ### Editors
 
-The Twitter account is currently managed by [bosch](https://twitter.com/_Bosch_).
+The accounts are currently managed by Christoph. Anyone is welcome to join.
 
 ---
 
@@ -71,7 +78,19 @@ Within each category, we use bullet lists to briefly summarize each item. Each p
 
 The top of each edition starts with an image that serves as a visual summary of the text content. The image is split into a grid of 8 units, each one showing a screenshot or other visual of a bullet item.
 
+Content is a reflection of what is happening in the community. There is no big effort to research and gather "original" content.
+
+The process is as follows:
+
+- We publish the newsletter every 3 weeks (except for breaks during long holidays)
+- After every publish, we create a new draft on Google Docs and share it in the [#spread-the-word](https://discord.gg/PGz2r2UAmE) channel with free edit rights for anyone
+- Anyone can add updates to the draft doc
+- A few days before publishing (usually the Friday before), the editors become active and start gathering additional material across Discord, Github, and social media
+- Going back and forth several times, the editors finalize on ~30 bullet points
+- The newsletter is published around noon
+- We post the link with a very short summary on Discord and social media. Social media posts include @ mentions of relevant people and projects
+
 ### Editors
 
-The newsletter is currently managed by Conor, Johns, and Christoph. Anyone is welcome to join.
+The newsletter is currently managed by Mo and Christoph. Anyone is welcome to join.