Skip to content

Commit 732971b

Browse files
committed
Merge remote-tracking branch 'upstream/main' into pre-commit-hook/fix-tables
2 parents 3de35e2 + aa79300 commit 732971b

File tree

464 files changed

+3461
-3184
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

464 files changed

+3461
-3184
lines changed

CONTRIBUTING.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ For example:
5252
> Something that requires warning here
5353
```
5454

55-
![Alert options](images/alerts.png)
55+
![Alert options](static/images/alerts.png)
5656

5757
### MDX Components
5858

@@ -63,6 +63,7 @@ There are a few reusable MDX components that can be used on pages with the `mdx`
6363
Collapsibles allow you to show/hide content on a page that may be secondary to the page's primary content. They have four fields that can be set: `title`, `description`, `icon`, and an `open` flag (which makes the collapsible element open by default).
6464

6565
Available options for `icon`:
66+
6667
- `"list"`
6768
- `"view"`
6869
- `"question"`
@@ -71,7 +72,7 @@ Available options for `icon`:
7172

7273
###### Example
7374

74-
![Collapsible MDX Component with the list icon](images/mdx-collapsible.png)
75+
![Collapsible MDX Component with the list icon](static/images/mdx-collapsible.png)
7576

7677
```markdown
7778
<Collapsible title="Title" description="Description text" icon="list">
@@ -85,7 +86,7 @@ Buttons are simply... clickable buttons. They take `href` and `color` as argumen
8586

8687
###### Example
8788

88-
![Button MDX Component](images/mdx-button.png)
89+
![Button MDX Component](static/images/mdx-button.png)
8990

9091
```markdown
9192
<LinkButton to="https://discord.com/developers/docs/getting-started" color="brand">click the button!</LinkButton>
@@ -97,7 +98,7 @@ Cards let you display links in a card format. They accept two arguments, `title`
9798

9899
###### Example
99100

100-
![Card MDX Component](images/mdx-card.png)
101+
![Card MDX Component](static/images/mdx-card.png)
101102

102103
```markdown
103104
<Card title="Card Title" link="https://discord.com/developers/docs/getting-started">

docs/activities/building-an-activity.mdx

Lines changed: 40 additions & 40 deletions
Large diffs are not rendered by default.

docs/activities/design-patterns.mdx

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ When in an Activity with others, make the actions and presence of the others vis
4949
- If a user has customized their server nickname or avatar, use their server nickname or avatar in game.
5050
- Show when a user is speaking in the voice call, or whether they're active or inactive.
5151

52-
![Speech bubbles in Bobble League](activities/bobble-bash.png)
52+
![Speech bubbles in Bobble League](images/activities/bobble-bash.png)
5353

5454

5555
### Respect user privacy
@@ -67,20 +67,20 @@ Make your app fast, easy to join, and maximize fun to launch a crowd favorite.
6767
- Surprise and delight is about caring about the small details of how a person experiences your work.
6868
- Put the right emotion in when they least expect it to deliver the magic.
6969

70-
![Bobble League](activities/bobble-league.png)
70+
![Bobble League](images/activities/bobble-league.png)
7171

7272
### Keep load times as low as possible
7373
- This allows for easier drop-in drop-out behavior for the large portion of mobile users on Discord.
74-
- See the below [Quality & Testing Recommendations](#DOCS_ACTIVITIES_DESIGN_PATTERNS/quality-and-testing) for key areas of minimum quality support and testing recommendations.
75-
- See the below [Technical Considerations](#DOCS_ACTIVITIES_DESIGN_PATTERNS/technical-considerations) for recommendations on how to partition loading and work with various development tools to reduce load times.
74+
- See the below [Quality & Testing Recommendations](/docs/activities/design-patterns#quality-and-testing) for key areas of minimum quality support and testing recommendations.
75+
- See the below [Technical Considerations](/docs/activities/design-patterns#technical-considerations) for recommendations on how to partition loading and work with various development tools to reduce load times.
7676
- Consider different screen sizes and orientations across desktop and mobile devices and make sure UI elements scale appropriately.
7777

7878
### Support drop-in, drop-out behavior
7979

8080
- Activities are frictionless to join and easy to discover, so you can expect that users will join mid-experience. Give those users something to do, even if it's just letting them spectate until they can join without being disruptive. In the same vein, users can leave without notice or become afk (away from keyboard). Handle these cases gracefully.
8181
- Create a case for users who have joined a call but have not yet started playing or engaging. Allow these users to "spectate" other users who are playing. This can also be helpful for Activities that have an ideal number in mind for play.
8282

83-
![Support drop-in, drop-out behavior in your Activity](activities/eights.png)
83+
![Support drop-in, drop-out behavior in your Activity](images/activities/eights.png)
8484

8585
### Make your app as available as possible
8686

@@ -105,7 +105,7 @@ Discord is a social platform where users talk to each other. Sharing and invites
105105
- Share photos or GIFs that capture moments of fun and memorable, or something to brag about. Don't make things shareable just to feature the activity.
106106
- Sharing a high score alone may not be very engaging, but sharing a really good move made in a game, or a collaborative drawing that creates a memory is a conversation starter and may make others want to join in on the fun.
107107

108-
![Shared Moment from Chess in the Park](activities/chess-victory.png)
108+
![Shared Moment from Chess in the Park](images/activities/chess-victory.png)
109109

110110
#### Activities in Text Channels
111111
- The Activity user interface, copy and user flows should not rely on people in voice to explain, organize, clarify, or instruct about how the activity works.

0 commit comments

Comments
 (0)