Skip to content

Commit

Permalink
Emojis must be Unicode, not specified as Markdown in channel headers (#…
Browse files Browse the repository at this point in the history
…7712)

* Emojis must be Unicode, not specified as Markdown in channel headers

* Update source/collaborate/channel-naming-conventions.rst

* Clarified Unicode workflow
  • Loading branch information
cwarnermm authored Jan 23, 2025
1 parent 1eae027 commit daf5fd5
Showing 1 changed file with 6 additions and 1 deletion.
7 changes: 6 additions & 1 deletion source/collaborate/channel-naming-conventions.rst
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,12 @@ Basic structure
- Channel names have a 64-character limit to ensure readability on both desktop and mobile devices.
- An additional 1024 characters are available for describing the channel's focus in the channel header and channel information pane.
- An additional 128 characters are available for a **Channel Purpose** that's visible in the channel header and the channel information pane.
- Channel names can include emojis. Specify the emoji by its name in the format ``:smile:``. We recommend prefixing channel names with emojis for the following reasons:
- Channel names can include standard Unicode emojis that are universally supported emojis that look the same (or similar) across platforms. Specify a Unicode emoji by positioning your cursor in the channel **Display Name** field and accessing the Unicode emoji picker for your operating system, as follows:

- On Windows press :kbd:`Windows` + :kbd:`.` or :kbd:`;` to open the Unicode emoji picker.
- On macOS, press :kbd:`Ctrl` + :kbd:`` + :kbd:`Space` to open the Unicode emoji picker.

We recommend prefixing channel names with emojis for the following reasons:

- Emojis can make it easier for users to quickly identify and manage channels, particularly in large workspaces with many channels.
- Sharing the same emoji across channels related to a specific category or function helps maintain organization and consistency across the workspace.
Expand Down

0 comments on commit daf5fd5

Please sign in to comment.