Repository: zulip/zulip

Issue:
Add "Writing messages" section to help center
In order to clearly document all the cool things you can do in a Zulip message, and make this information easy to find, we should add a new "Writing messages" help center section (just above "Sending messages").

Tasks:

- [ ] Move the following pages from "Sending messages" to "Writing messages" (we can preserve the order):

[Message formatting](https://zulip.com/help/format-your-message-using-markdown)
[Mention a user or group](https://zulip.com/help/mention-a-user-or-group)
[Emoji and emoticons](https://zulip.com/help/emoji-and-emoticons)
[Start a video call](https://zulip.com/help/start-a-call)
[Share and upload files](https://zulip.com/help/share-and-upload-files)
[Quote and reply](https://zulip.com/help/quote-and-reply)
[Code blocks](https://zulip.com/help/code-blocks)
[Add GIFs in your message](https://zulip.com/help/animated-gifs-from-giphy)
[Create a poll](https://zulip.com/help/create-a-poll)

- [ ] Make sure the pages on that list that overlap with "Message formatting" use `include` blocks -- e.g., I noticed that "Code blocks" duplicates content.

- [ ] Create a new page corresponding to each section of `/help/format-your-message-using-markdown` that currently doesn't have a page.
   - Use `include` blocks; we want to keep the all-in-one reference page as well.
   - Page names will be a bit different from section names, e.g., "Insert a link" for "Links".

[CZO discussion](https://chat.zulip.org/#narrow/stream/19-documentation/topic/message.20formatting/near/1497280)


Discussion:
Hello @zulip/server-user-docs members, this issue was labeled with the "area: documentation (user)" label, so you may want to check it out!

<!-- areaLabelAddition -->

@drrosa Would you be up for taking this on?
Follow-up issue: #24209

Hello Alya is it ok if I take up this issue ?

@zulipbot claim
Welcome to Zulip, @MashyBasker! We just sent you an invite to collaborate on this repository at https://github.com/zulip/zulip/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip!

Here's some tips to get you off to a good start:

- Join me on the [Zulip developers' server](https://chat.zulip.org), to get help, chat about this issue, and meet the other developers.
- [Unwatch this repository](https://help.github.com/articles/unwatching-repositories/), so that you don't get 100 emails a day.

As you work on this issue, you'll also want to refer to the [Zulip code contribution guide](https://zulip.readthedocs.io/en/latest/contributing/index.html), as well as the rest of the developer documentation on that site.

See you on the other side (that is, the pull request side)!

Hi @MashyBasker , when do you plan to put up a PR for this issue? We'd like to get it done soon, so it would be best if @drrosa worked on it if it will be more than another couple of days. Thanks!
> 

ok sure
@zulipbot abandon
@zulipbot claim

Resolving patch:
diff --git a/zerver/lib/markdown/tabbed_sections.py b/zerver/lib/markdown/tabbed_sections.py
--- a/zerver/lib/markdown/tabbed_sections.py
+++ b/zerver/lib/markdown/tabbed_sections.py
@@ -93,6 +93,8 @@
     "user": "User",
     "bot": "Bot",
     "on-sign-up": "On sign-up",
+    "via-markdown": "Via Markdown",
+    "via-compose-box-buttons": "Via compose box buttons",
 }
 
 


Test patch: