mirror of
https://github.com/status-im/wiki.status.im.git
synced 2025-02-23 01:28:19 +00:00
minor grammatical changes
This commit is contained in:
parent
aee5081aaa
commit
17b63dad07
@ -5,11 +5,11 @@ This is a list of practical tips and suggestions on how you can take part in, he
|
||||
If you haven’t done so yet, please read our [Mission and Core Values](../getting-started/mission-and-core-values.md) and ensure you follow our [Code of Conduct](../getting-started/code-of-conduct.md), as these are closely aligned.
|
||||
|
||||
|
||||
## Get involved with the status.im community
|
||||
## How to Get Involved
|
||||
|
||||
- at the moment much of the community communication takes place on slack. A first step to getting involved can be as simple as joining [status-im.slack](status-im.slack.com) and saying “hi”.
|
||||
- At the moment much of the community communication takes place on slack. A first step to getting involved can be as simple as joining [our Slack](status-im.slack.com) and saying “hi” (we're friendly people!).
|
||||
|
||||
- Take a look around the [Slack](http://slack.status.im) channels, where you will find #dev-status, #dapp-chat, #lll etc.
|
||||
- Take a look around the Slack channels, where you will find #dev-status, #dapp-chat, #lll etc.
|
||||
|
||||
- When you get to know people in the community who have interests or skills then let them know about or invite them to join the channels that play to their strengths.
|
||||
|
||||
@ -18,7 +18,7 @@ If you haven’t done so yet, please read our [Mission and Core Values](../getti
|
||||
* The description should help others make a quick decision which channels they need to join.
|
||||
|
||||
|
||||
## Highlighting / Managing Needs
|
||||
## Highlighting & Managing Needs
|
||||
|
||||
- Share your ideas on how we can make the list of tasks and needed contributions more easily visible. The more accessible and manageable tasks become to the community the better.
|
||||
|
||||
|
@ -1,24 +0,0 @@
|
||||
This document is a guide to contributors and community members on how to maintain the "brand" and present Status.im both to the wider public
|
||||
and when integrating external content within Status
|
||||
|
||||
|
||||
## Brand guidlines
|
||||
|
||||
|
||||
|
||||
## DApps in status
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
##Appearance
|
||||
|
||||
- Try to maintain a professional appearance, whether that is profile pictures or site design, this makes us more attractive.
|
||||
|
||||
STUB
|
@ -20,7 +20,7 @@ pages:
|
||||
- Introduction: 'contributing/development/introduction.md'
|
||||
- Building Status: 'contributing/development/building-status.md'
|
||||
- Adding DApps: 'contributing/development/adding-dapps.md'
|
||||
- UX & Design: 'contributing/ux-and-design.md'
|
||||
- Design Guidelines: 'contributing/design-guidelines.md'
|
||||
- Testing & Feedback: 'contributing/testing-and-feedback.md'
|
||||
- Documenting: 'contributing/documenting.md'
|
||||
- Outreach: 'contributing/outreach.md'
|
||||
|
Loading…
x
Reference in New Issue
Block a user