mirror of
https://github.com/zulip/zulip.git
synced 2025-10-23 04:52:12 +00:00
help: Make loose lists tight for help center files.
In our current implementation, loose lists and tight lists look the same visually. Loose lists are lists with blank lines between list items, and the contents of a list item should be enclosed in a paragraph tag in that case. For unordered lists, paragraph tags have a bottom margin in starlight and thus looses lists look much more spaced out than tight lists. That is not the behaviour we had in mind while writing the documentation, the reason we had all these loose lists is to make the documentation easy to write and read. So we attempt to remove all the blank lines and fix the problem at source. Since paragraph tags are used for other purposes in a list in starlight, it won't be a wise decision to let the source be as is and just change things in css, other expected behaviours might break in that case. See this topic for more details: https://chat.zulip.org/#narrow/channel/19-documentation/topic/new.20help.20center.3A.20regressions/near/2226084 All the changes were made by a one-off script which has not been commited to the repo. The script wasn't perfect and could not decide between blank lines that make a list loose vs blank lines necessary for a sub-list or a code block inside a list item. A manual review of all the changes was done before making this commit to ensure that no unintended changes were made to the help center files.
This commit is contained in:
Shubham Padia
committed by
Tim Abbott
Tim Abbott
parent
2f4dd72076
commit
7ce87c66ac
@@ -186,15 +186,12 @@ interest (`django/django`) that is in a different organization.
|
||||
* Specific linkifier (ordered before the general linkifier)
|
||||
* Pattern: `django#(?P<id>[0-9]+)`
|
||||
* URL template: `https://github.com/django/django/pull/{id}`
|
||||
|
||||
* General linkifier
|
||||
* Pattern: `(?P<repo>[a-zA-Z0-9_-]+)#(?P<id>[0-9]+)`
|
||||
* URL template: `https://github.com/zulip/{repo}/pull/{id}`
|
||||
|
||||
* Example matching both linkifiers; specific linkifier takes precedence:
|
||||
* Original text: `django#123`
|
||||
* Automatically links to: `https://github.com/django/django/pull/123`
|
||||
|
||||
* Example matching only the general linkifier:
|
||||
* Original text: `zulip-desktop#123`
|
||||
* Automatically links to: `https://github.com/zulip/zulip-desktop/pull/123`
|
||||
|
||||
@@ -24,12 +24,9 @@ Each bot has a **name**, **profile picture**, **email**, **bot type** and **API
|
||||
|
||||
* The **name** and **profile picture** play the same role they do for human users. They
|
||||
are the most visible attributes of a bot.
|
||||
|
||||
* The **email** is not used for anything, and will likely be removed in a
|
||||
future version of Zulip.
|
||||
|
||||
* The **bot type** determines what the bot can and can't do (see below).
|
||||
|
||||
* The **API key** is how the bot identifies itself to Zulip. Anyone with the
|
||||
bot's API key can impersonate the bot.
|
||||
|
||||
@@ -51,20 +48,16 @@ A few more details:
|
||||
|
||||
* Bots can send messages to any channel that their owner can,
|
||||
inheriting their owner's [sending permissions](/help/channel-posting-policy).
|
||||
|
||||
* Bots can be subscribed to channels, and their role can be modified if
|
||||
they need to have permission to do administrative actions.
|
||||
|
||||
* [Channel permissions](/help/channel-permissions) are the same for bots
|
||||
as for other users. Therefore, for private channels with protected
|
||||
history, a bot can only access messages sent after it was subscribed
|
||||
to the channel.
|
||||
|
||||
* **Generic**: A generic bot is like a normal Zulip user account that
|
||||
cannot log in via a browser. Note that if you truly want to
|
||||
impersonate yourself (e.g., write messages that come from your Zulip
|
||||
account), you'll need to use your **personal API key**.
|
||||
|
||||
* **Outgoing webhook**: The bot can read direct messages where the bot is a
|
||||
participant, and channel messages where the bot is [mentioned](/help/mention-a-user-or-group). When the
|
||||
bot is DM'd or mentioned, it POSTs the message content to a URL of your
|
||||
|
||||
@@ -163,20 +163,16 @@ languages:
|
||||
|
||||
* You can configure multiple playgrounds for a given language; if you do that,
|
||||
the user will get to choose which playground to open the code in.
|
||||
|
||||
* The **Language** field is the human-readable Pygments language name for that
|
||||
programming language. The language tag for a code block is internally mapped
|
||||
to these human-readable Pygments names; e.g., `py3` and `py` are mapped to
|
||||
`Python`. One can use the typeahead (which appears when you type something
|
||||
or just click on the language field) to look up the Pygments name.
|
||||
|
||||
* The links for opening code playgrounds are always constructed by substituting
|
||||
the URL-encoded contents of the code block into `code` variable in the URL template.
|
||||
The URL template is required to contain exactly one variable named `code`.
|
||||
|
||||
* Code playground sites do not always clearly document their URL format; often
|
||||
you can just get the prefix from your browser's URL bar.
|
||||
|
||||
* You can also use a custom language name to implement simple integrations.
|
||||
For example, a code block tagged with the "language" `send_tweet` could be
|
||||
used with a "playground" that sends the content of the code block as a Tweet.
|
||||
|
||||
@@ -18,7 +18,6 @@ preference settings, including the following:
|
||||
messages](/help/read-receipts)
|
||||
* Allowing others to see when the user is [typing a
|
||||
message](/help/typing-notifications)
|
||||
|
||||
* Preferences:
|
||||
* [Language](/help/change-your-language)
|
||||
* [Time format](/help/change-the-time-format)
|
||||
@@ -30,7 +29,6 @@ preference settings, including the following:
|
||||
([Inbox](/help/inbox) vs.
|
||||
[Recent conversations](/help/recent-conversations) vs.
|
||||
[Combined feed](/help/reading-strategies#combined-feed))
|
||||
|
||||
* Notification settings:
|
||||
* What types of messages [trigger notifications][default-notifications]
|
||||
* Which topics users will [automatically follow](/help/follow-a-topic). This
|
||||
|
||||
@@ -26,9 +26,7 @@ organization](/help/configure-default-new-user-settings) to
|
||||
|
||||
- The **Inbox** view works best if you regularly clear all unread messages in
|
||||
channels you follow.
|
||||
|
||||
- **Recent conversations** works well for getting an overview of recent activity.
|
||||
|
||||
- **Combined feed** is convenient for low-traffic organizations, or for skimming
|
||||
messages as they come in.
|
||||
|
||||
|
||||
@@ -13,10 +13,8 @@ automated messages and invitation emails. This setting:
|
||||
notices](/help/configure-automated-notices) that are sent to channels, including
|
||||
both the topic name and message content. (Automated messages sent to a single
|
||||
user will use that user's preferred language).
|
||||
|
||||
* Determines the language used for outgoing
|
||||
[invitation emails](/help/invite-new-users).
|
||||
|
||||
* Is used as the default language for new user accounts when Zulip
|
||||
cannot detect their language preferences from their browser,
|
||||
including all users [created via the Zulip API][api-create-user].
|
||||
|
||||
@@ -23,16 +23,13 @@ feedback.
|
||||
support](mailto:support@zulip.com).
|
||||
* Response time: Usually within 1-3 business days, or within one business
|
||||
day for paid customers.
|
||||
|
||||
* For support requests regarding your **self-hosted server**:
|
||||
|
||||
* **Business** and **Enterprise** plan customers can request interactive
|
||||
chat support in the [Zulip development community](#zulip-community),
|
||||
or [email Zulip support](mailto:support@zulip.com). Phone support is
|
||||
available for Enterprise customers upon request.
|
||||
|
||||
* Response time: Usually within one business day.
|
||||
|
||||
* **Free** and **Community** plan customers can ask for help in the
|
||||
[Zulip development community](#zulip-community). You will usually get a
|
||||
friendly reply within 1-3 business days.
|
||||
@@ -55,7 +52,6 @@ for your organization.
|
||||
* Response time: Usually within 1-3 business days in the [Zulip development
|
||||
community](#zulip-community) or by email, or within one week [on
|
||||
GitHub](https://github.com/zulip).
|
||||
|
||||
* You can [**request
|
||||
features**](https://zulip.readthedocs.io/en/latest/contributing/suggesting-features.html)
|
||||
or [**share
|
||||
@@ -64,7 +60,6 @@ for your organization.
|
||||
* Response time: Usually within 1-3 business days in the [Zulip development
|
||||
community](#zulip-community) or by email, or within one week [on
|
||||
GitHub](https://github.com/zulip).
|
||||
|
||||
* To **report issues or share feedback privately**, contact
|
||||
[feedback@zulip.com](mailto:feedback@zulip.com). This works well if you'd like
|
||||
to include details about your organization that shouldn't be posted in public.
|
||||
|
||||
@@ -11,18 +11,15 @@
|
||||
* It's often best to start with just a few channels, and add more as
|
||||
needed. For small teams, you can start with the default channels
|
||||
and go from there.
|
||||
|
||||
* A channel's name can be in any language, and can include spaces, punctuation,
|
||||
and Unicode emoji. For large organizations, we recommend using a consistent naming
|
||||
scheme, like `#marketing/<name>` or `#mk/<name>` for all channels
|
||||
pertaining to the marketing team, `#help/<team name>` for
|
||||
`<team name>`'s internal support channel, etc.
|
||||
|
||||
* You can [pin reference information](/help/pin-information), such as important
|
||||
messages or topics, and external references, in the
|
||||
[description](/help/view-channel-information#view-channel-description) for a
|
||||
channel.
|
||||
|
||||
* For open source projects or other volunteer organizations, consider
|
||||
adding default channels like **#announce** for announcements, **#new
|
||||
members** for new members to introduce themselves and be welcomed,
|
||||
|
||||
@@ -6,17 +6,13 @@ A few settings to highlight:
|
||||
|
||||
* Decide [who can invite new users][who-can-invite], or whether
|
||||
[anyone can join without an invitation][who-can-join].
|
||||
|
||||
* [Set visibility for users' email addresses][email-address-visibility].
|
||||
|
||||
* If your organization uses a programming language, set the [default
|
||||
language for code blocks][default-code-block-language]. Also
|
||||
consider setting up [code playgrounds][code-playgrounds].
|
||||
|
||||
* If your organization uses code repositories, [set up
|
||||
linkifiers](/help/add-a-custom-linkifier) to make it easy to link to
|
||||
issues (e.g., just by typing #1234 for issue 1234).
|
||||
|
||||
* [Add custom emoji](/help/custom-emoji), including your organization's logo.
|
||||
|
||||
For many other settings, e.g., [message][message-editing-permissions] and
|
||||
|
||||
@@ -8,22 +8,17 @@ When you deactivate a user:
|
||||
|
||||
* The user will be immediately logged out of all Zulip sessions, including
|
||||
desktop, web and mobile apps.
|
||||
|
||||
* The user's credentials for logging in will no longer work, including password
|
||||
login and [any other login options](/help/configure-authentication-methods)
|
||||
enabled in your organization.
|
||||
|
||||
* The user's [bots](/help/bots-overview) will be deactivated.
|
||||
|
||||
* [Email invitations and invite links](/help/invite-new-users) created by the
|
||||
user will be disabled.
|
||||
|
||||
* Other users will be able to see that the user has been deactivated (e.g., on
|
||||
their [user card](/help/user-cards)). In sidebars and elsewhere, a user's
|
||||
[availability](/help/status-and-availability) will be replaced with a
|
||||
deactivated icon
|
||||
(<span class="user-circle user-circle-deactivated zulip-icon zulip-icon-user-circle-deactivated"></span>).
|
||||
|
||||
* Even if your organization [allows users to join without an
|
||||
invitation](/help/restrict-account-creation#set-whether-invitations-are-required-to-join),
|
||||
this user will not be able to rejoin with the same email account.
|
||||
|
||||
@@ -40,11 +40,9 @@ account.
|
||||
|
||||
* Your [user card](/help/user-cards) will have a notice indicating that your
|
||||
account has been deactivated.
|
||||
|
||||
* Deactivating your account won't delete messages you've sent or files
|
||||
you've shared. If permitted in your organization, delete content you'd
|
||||
like to remove before deactivating your account.
|
||||
|
||||
* Any bots that you maintain will be disabled.
|
||||
|
||||
|
||||
|
||||
@@ -6,9 +6,7 @@ We generally recommend against deleting topics, but there are a few
|
||||
situations in which it can be useful:
|
||||
|
||||
* Clearing out test messages after setting up an organization.
|
||||
|
||||
* Clearing out messages from an overly enthusiastic bot.
|
||||
|
||||
* Managing abuse.
|
||||
|
||||
In most other cases, [renaming a topic](/help/rename-a-topic) is often a
|
||||
|
||||
@@ -16,7 +16,6 @@ available for all Zulip organizations:
|
||||
channel](/help/channel-permissions#private-channels) messages and [direct
|
||||
messages](/help/direct-messages). This export includes user settings and
|
||||
channel subscriptions.
|
||||
|
||||
* [**Standard
|
||||
export**](#export-for-migrating-to-zulip-cloud-or-a-self-hosted-server):
|
||||
Everything in the export of public data, plus all the [private
|
||||
@@ -32,7 +31,6 @@ Standard][plans] and [Zulip Cloud Plus][plans] customers:
|
||||
|
||||
* [**Full export without member consent**](#full-export-without-member-consent):
|
||||
All the data in the organization.
|
||||
|
||||
* [**Compliance export**](#compliance-export): A targeted, human-readable export
|
||||
of messages matching some combination of criteria (e.g., sender, recipient,
|
||||
message keyword, or timestamp).
|
||||
|
||||
@@ -11,14 +11,11 @@ It's easy to prioritize catching up on followed topics. You can:
|
||||
|
||||
- [Configure](/help/follow-a-topic#configure-notifications-for-followed-topics)
|
||||
how you get notified about new messages for topics you follow.
|
||||
|
||||
- Use the <kbd>Shift</kbd> + <kbd>N</kbd> [keyboard
|
||||
shortcut](/help/keyboard-shortcuts) to go to the next unread followed topic.
|
||||
|
||||
- Filter the [**inbox**](/help/inbox) and [**recent
|
||||
conversations**](/help/recent-conversations) views to only show followed
|
||||
topics.
|
||||
|
||||
- See which topics you are following in the **left sidebar**.
|
||||
|
||||
You can use followed topics for a variety of workflows:
|
||||
|
||||
@@ -261,7 +261,6 @@ keep in mind about the import process:
|
||||
visibility](/help/configure-email-visibility),
|
||||
[message editing permissions](/help/restrict-message-editing-and-deletion),
|
||||
and [how users can join your organization](/help/restrict-account-creation).
|
||||
|
||||
- Mattermost's user roles are mapped to Zulip's [user
|
||||
roles](/help/user-roles) in the following way:
|
||||
|
||||
@@ -272,11 +271,9 @@ keep in mind about the import process:
|
||||
|
||||
- Mattermost's export tool does not support exporting user avatars or message
|
||||
edit history.
|
||||
|
||||
- Direct messages will only be imported from Mattermost workspaces containing
|
||||
a single team. This is because Mattermost's data exports do not associate
|
||||
direct messages with a specific Mattermost team.
|
||||
|
||||
- Messages in threads are imported, but they are not explicitly marked as
|
||||
being in a thread.
|
||||
|
||||
|
||||
@@ -107,10 +107,8 @@ keep in mind about the import process:
|
||||
visibility](/help/configure-email-visibility),
|
||||
[message editing permissions](/help/restrict-message-editing-and-deletion),
|
||||
and [how users can join your organization](/help/restrict-account-creation).
|
||||
|
||||
- Rocket.Chat does not export user settings, so users in your organization may
|
||||
want to [customize their account settings](/help/getting-started-with-zulip).
|
||||
|
||||
- Rocket.Chat user roles are mapped to Zulip's [user
|
||||
roles](/help/user-roles) in the following way:
|
||||
|
||||
@@ -121,24 +119,17 @@ keep in mind about the import process:
|
||||
| Guest | Guest |
|
||||
|
||||
- User avatars are not imported.
|
||||
|
||||
- Default channels for new users are not imported.
|
||||
|
||||
- Starred messages are not imported.
|
||||
|
||||
- Messages longer than Zulip's limit of 10,000 characters are not
|
||||
imported.
|
||||
|
||||
- Livechat channels/messages are not imported.
|
||||
|
||||
- Messages from Rocket.Chat Discussions are imported as topics
|
||||
inside the Zulip channel corresponding to the parent channel of the
|
||||
Rocket.Chat Discussion.
|
||||
|
||||
- Messages from Rocket.Chat Discussions having direct channels
|
||||
(i.e. direct messages) as their parent are imported as normal
|
||||
direct messages in Zulip.
|
||||
|
||||
- While Rocket.Chat Threads are in general imported as separate
|
||||
topics, Rocket.Chat Threads within Rocket.Chat Discussions are
|
||||
imported as normal messages within the topic containing that
|
||||
|
||||
@@ -148,10 +148,8 @@ in mind about the import process:
|
||||
visibility](/help/configure-email-visibility),
|
||||
[message editing permissions](/help/restrict-message-editing-and-deletion),
|
||||
and [how users can join your organization](/help/restrict-account-creation).
|
||||
|
||||
- Slack does not export user settings, so users in your organization may want to
|
||||
[customize their account settings](/help/getting-started-with-zulip).
|
||||
|
||||
- Slack's user roles are mapped to Zulip's [user
|
||||
roles](/help/user-roles) in the following way:
|
||||
|
||||
@@ -167,7 +165,6 @@ in mind about the import process:
|
||||
|
||||
- Slack threads are imported as topics with names that include snippets of the
|
||||
original message, such as "2023-05-30 Hi, can anyone reply if you're o…".
|
||||
|
||||
- Message edit history and `@user joined #channel_name` messages are not imported.
|
||||
|
||||
## Clean up after the Slack export
|
||||
|
||||
@@ -5,7 +5,6 @@ of the Zulip app. For best results:
|
||||
|
||||
- The logo should be a wide rectangle image with an 8:1 width to height ratio.
|
||||
It will be displayed at 200×25 pixels, or more on high-resolution displays.
|
||||
|
||||
- Make sure your logo has a transparent background, and trim any bordering
|
||||
whitespace.
|
||||
|
||||
|
||||
@@ -5,11 +5,9 @@ There are three types of channels in Zulip:
|
||||
joining and viewing messages requires being invited. You can choose
|
||||
whether new subscribers can see messages sent before they were
|
||||
subscribed.
|
||||
|
||||
* [Public channels](/help/channel-permissions#public-channels)
|
||||
(indicated by <i class="zulip-icon zulip-icon-hashtag"></i>), which
|
||||
are open to everyone in your organization other than guests.
|
||||
|
||||
* [Web-public channels](/help/channel-permissions#web-public-channels)
|
||||
(indicated by <i class="zulip-icon zulip-icon-globe"></i>), where
|
||||
anyone on the Internet can see messages without creating an account.
|
||||
|
||||
@@ -3,12 +3,9 @@ There are several ways to use an emoji in your message:
|
||||
|
||||
- [Enter an emoji name](/help/emoji-and-emoticons#use-an-emoji-in-your-message)
|
||||
surrounded by `:`, with help from autocomplete suggestions.
|
||||
|
||||
- [Select an emoji from the emoji
|
||||
picker](/help/emoji-and-emoticons#use-an-emoji-in-your-message)
|
||||
|
||||
- [Use an emoticon](/help/emoji-and-emoticons#use-an-emoticon)
|
||||
|
||||
- [Paste an emoji](/help/emoji-and-emoticons#use-an-emoji-in-your-message)
|
||||
|
||||
You can [add custom emoji](/help/custom-emoji) for your organization. Like
|
||||
|
||||
@@ -3,7 +3,6 @@ To perform this export, your organization must meet the following requirements:
|
||||
- You are a paid [Zulip Cloud Standard](https://zulip.com/plans/) or [Zulip
|
||||
Cloud Plus](https://zulip.com/plans/) customer. In rare cases, exceptions may
|
||||
be made in case of due legal process.
|
||||
|
||||
- You have authority to read members' [direct messages](/help/direct-messages).
|
||||
Typically, this will be because your Zulip organization is administered by a
|
||||
corporation, and you are an official representative of that corporation.
|
||||
|
||||
@@ -2,19 +2,16 @@
|
||||
followed topics at the start of the day, and whenever you want to
|
||||
spend a few minutes checking on on the conversations that need
|
||||
your attention.
|
||||
|
||||
- No more stressing about missing a reply to your message in channels
|
||||
you don't regularly read. You can [automatically
|
||||
follow](/help/follow-a-topic#automatically-follow-topics) topics you
|
||||
start or participate in.
|
||||
|
||||
- You can also [mute](/help/mute-a-channel) the channels you don't
|
||||
regularly read, and [automatically follow or
|
||||
unmute](/help/follow-a-topic#automatically-follow-topics) topics you
|
||||
start or participate in. In muted channels, topics you follow are
|
||||
automatically treated as [unmuted](/help/mute-a-topic), so it will
|
||||
be easy to see when someone responds to your message.
|
||||
|
||||
- If you like, follow just the topics where your prompt attention is
|
||||
needed, and [enable desktop and mobile
|
||||
notifications](/help/follow-a-topic#configure-notifications-for-followed-topics)
|
||||
|
||||
@@ -41,7 +41,6 @@
|
||||
email [support@zulip.com](mailto:support@zulip.com) to request this. Server
|
||||
administrators for self-hosted organizations should follow [these
|
||||
instructions](/help/import-from-slack#send-password-reset-emails-to-all-users).
|
||||
|
||||
- Let users know that they can [request a password
|
||||
reset](/help/change-your-password#if-youve-forgotten-or-never-had-a-password)
|
||||
on your organization's login page.
|
||||
|
||||
@@ -1,15 +1,11 @@
|
||||
On the billing page for an active paid plan you can:
|
||||
|
||||
- View your past invoices.
|
||||
|
||||
- View and update the billing details displayed on invoices and receipts
|
||||
for future payments.
|
||||
|
||||
- If you pay for your plan by credit card, update your card's payment
|
||||
details.
|
||||
|
||||
- Change your billing frequency to be monthly or annual.
|
||||
|
||||
- If you opted for [manual license
|
||||
management](#how-does-manual-license-management-work), you can [update
|
||||
the number of licenses](#manually-update-number-of-licenses)
|
||||
|
||||
@@ -5,23 +5,18 @@
|
||||
|
||||
- Get the [mobile and desktop apps](/apps/). Zulip also works great in a
|
||||
[browser](/help/supported-browsers).
|
||||
|
||||
- [Add a profile picture](/help/change-your-profile-picture) and
|
||||
[edit your profile information](/help/edit-your-profile) to tell others
|
||||
about yourself.
|
||||
|
||||
- [Review your preferences](/help/review-your-settings#review-your-preferences).
|
||||
You can [switch between light and dark theme](/help/dark-theme), [customize
|
||||
the font size](/help/font-size), [pick your favorite emoji
|
||||
theme](/help/emoji-and-emoticons#change-your-emoji-set), [change your
|
||||
language](/help/change-your-language), and make other tweaks to your Zulip
|
||||
experience.
|
||||
|
||||
- [Browse and subscribe to channels](/help/introduction-to-channels#browse-and-subscribe-to-channels).
|
||||
|
||||
- Decide whether you want <kbd>Enter</kbd> [to send your message or add a
|
||||
new line](/help/configure-send-message-keys).
|
||||
|
||||
- [Configure your notifications](/help/review-your-settings#review-your-notification-settings)
|
||||
to work the way you do. If you're joining a low traffic organization and
|
||||
aren't using the desktop app, consider sending all messages to email.
|
||||
|
||||
@@ -7,7 +7,6 @@ Prior to inviting users to your organization, it is recommended that administrat
|
||||
|
||||
* Configure [default settings](/help/configure-default-new-user-settings) for
|
||||
new users.
|
||||
|
||||
* Configure the [organization language for automated messages and invitation
|
||||
emails][org-lang] for your organization.
|
||||
|
||||
@@ -15,11 +14,9 @@ When you invite users, you can:
|
||||
|
||||
* Set the [role](/help/user-roles) that they will have when
|
||||
they join.
|
||||
|
||||
* Configure which [channels](/help/introduction-to-channels) they will be
|
||||
subscribed to. The organization's [default
|
||||
channels](/help/set-default-channels-for-new-users) will be preselected.
|
||||
|
||||
* Configure which [groups](/help/user-groups) they will be added to.
|
||||
|
||||
Organization administrators can
|
||||
|
||||
@@ -48,7 +48,6 @@ link via another method.
|
||||
* If you are joining multiple Zulip organizations, we recommend
|
||||
using the [Zulip Desktop app](../apps/). The desktop app makes it easy to
|
||||
[switch between different organizations](/help/switching-between-organizations).
|
||||
|
||||
* If your company uses single sign-on (SSO) authentication for Zulip,
|
||||
these instructions may not apply. Try going to your company's Zulip URL
|
||||
to see if there are instructions there; otherwise contact your manager
|
||||
|
||||
@@ -19,41 +19,27 @@ in the Zulip app to add more to your repertoire as needed.
|
||||
|
||||
* **Reply to message**: <kbd>R</kbd> or <kbd>Enter</kbd> — Reply to the
|
||||
selected message (outlined in blue).
|
||||
|
||||
* **New channel message**: <kbd>C</kbd> — Start a new topic in the current
|
||||
channel.
|
||||
|
||||
* **New direct message**: <kbd>X</kbd>
|
||||
|
||||
* **Paste formatted text**: <kbd>Ctrl</kbd> + <kbd>V</kbd>
|
||||
|
||||
* **Paste as plain text**: <kbd data-mac-following-key="⌥">Ctrl</kbd> +
|
||||
<kbd>Shift</kbd> + <kbd>V</kbd>. You can also paste formatted text with
|
||||
<kbd>Ctrl</kbd> + <kbd>V</kbd>, and press <kbd>Ctrl</kbd> + <kbd>Z</kbd> to
|
||||
remove formatting.
|
||||
|
||||
* **Cancel compose and save draft**: <kbd>Esc</kbd> or
|
||||
<kbd data-mac-key="Ctrl">Ctrl</kbd> + <kbd>[</kbd> — Close the compose box
|
||||
and save the unsent message as a draft.
|
||||
|
||||
* **View drafts**: <kbd>D</kbd> — Use the arrow keys and <kbd>Enter</kbd>
|
||||
to restore a draft. Press <kbd>D</kbd> again to close.
|
||||
|
||||
* **Next message**: <kbd class="arrow-key">↓</kbd> or <kbd>J</kbd>
|
||||
|
||||
* **Last message**: <kbd>End</kbd> or <kbd>Shift</kbd> + <kbd>G</kbd> —
|
||||
Also marks all messages in the current view as read.
|
||||
|
||||
* **Next unread topic**: <kbd>N</kbd>
|
||||
|
||||
* **Next unread followed topic**: <kbd>Shift</kbd> + <kbd>N</kbd>
|
||||
|
||||
* **Next unread direct message**: <kbd>P</kbd>
|
||||
|
||||
* **Search messages**: <kbd>/</kbd>
|
||||
|
||||
* **Toggle keyboard shortcuts view**: <kbd>?</kbd>
|
||||
|
||||
* **Go to your home view**: <kbd data-mac-key="Ctrl">Ctrl</kbd> + <kbd>[</kbd>
|
||||
(or <kbd>Esc</kbd>, [if enabled][disable-escape])
|
||||
until you are in your [home view](/help/configure-home-view).
|
||||
@@ -62,9 +48,7 @@ in the Zulip app to add more to your repertoire as needed.
|
||||
## Search
|
||||
|
||||
* **Search messages**: <kbd>/</kbd> or <kbd>Ctrl</kbd> + <kbd>K</kbd>
|
||||
|
||||
* **Filter channels**: <kbd>Q</kbd>
|
||||
|
||||
* **Filter users**: <kbd>W</kbd>
|
||||
|
||||
## Scrolling
|
||||
@@ -72,16 +56,11 @@ in the Zulip app to add more to your repertoire as needed.
|
||||
* **Last message**: <kbd>End</kbd> or <kbd>Fn</kbd> + <kbd class="arrow-key">→</kbd>
|
||||
or <kbd>Shift</kbd> + <kbd>G</kbd> — Also marks all messages in the current view
|
||||
as read.
|
||||
|
||||
* **First message**: <kbd>Home</kbd> or <kbd>Fn</kbd> + <kbd class="arrow-key">←</kbd>
|
||||
|
||||
* **Previous message**: <kbd class="arrow-key">↑</kbd> or <kbd>K</kbd>
|
||||
|
||||
* **Next message**: <kbd class="arrow-key">↓</kbd> or <kbd>J</kbd>
|
||||
|
||||
* **Scroll up**: <kbd>PgUp</kbd> or <kbd>Fn</kbd> + <kbd class="arrow-key">↑</kbd>
|
||||
or <kbd>Shift</kbd> + <kbd>K</kbd>
|
||||
|
||||
* **Scroll down**: <kbd>PgDn</kbd> or <kbd>Fn</kbd> + <kbd class="arrow-key">↓</kbd>
|
||||
or <kbd>Shift</kbd> + <kbd>J</kbd> or <kbd>Spacebar</kbd>
|
||||
|
||||
@@ -89,56 +68,35 @@ in the Zulip app to add more to your repertoire as needed.
|
||||
|
||||
* **Go back through viewing history**: <kbd data-mac-key="⌘">Alt</kbd> +
|
||||
<kbd class="arrow-key">←</kbd>
|
||||
|
||||
* **Go forward through viewing history**: <kbd data-mac-key="⌘">Alt</kbd> +
|
||||
<kbd class="arrow-key">→</kbd>
|
||||
|
||||
* **Go to next unread topic**: <kbd>N</kbd>
|
||||
|
||||
* **Go to next unread followed topic**: <kbd>Shift</kbd> + <kbd>N</kbd>
|
||||
|
||||
* **Go to next unread direct message**: <kbd>P</kbd>
|
||||
|
||||
* **Go to topic or DM conversation**: <kbd>S</kbd>
|
||||
|
||||
* **Go to channel feed from topic view**: <kbd>S</kbd>
|
||||
|
||||
* **Go to direct message feed**: <kbd>Shift</kbd> + <kbd>P</kbd>
|
||||
|
||||
* **Go to list of topics for the current channel**: <kbd>Y</kbd>
|
||||
|
||||
* **Zoom to message in conversation context**: <kbd>Z</kbd> — This view does not mark messages as read.
|
||||
|
||||
* **Cycle between channel views**: <kbd>Shift</kbd> + <kbd>A</kbd>
|
||||
(previous) and <kbd>Shift</kbd> + <kbd>D</kbd> (next)
|
||||
|
||||
* **Go to inbox**: <kbd>Shift</kbd> + <kbd>I</kbd> — Shows conversations with unread messages.
|
||||
|
||||
* **Go to recent conversations**: <kbd>T</kbd>
|
||||
|
||||
* **Go to combined feed**: <kbd>A</kbd> — Shows all unmuted messages.
|
||||
|
||||
* **Go to starred messages**: <kbd>*</kbd>
|
||||
|
||||
* **Go to the conversation you are composing to**: <kbd>Ctrl</kbd> + <kbd>.</kbd>
|
||||
|
||||
## Composing messages
|
||||
|
||||
* **New channel message**: <kbd>C</kbd> — For starting a new topic in a
|
||||
channel.
|
||||
|
||||
* **New direct message**: <kbd>X</kbd>
|
||||
|
||||
* **Reply to message**: <kbd>R</kbd> or <kbd>Enter</kbd> — Reply to the
|
||||
selected message (outlined in blue). Same behavior as clicking on the
|
||||
message.
|
||||
|
||||
* **Quote message**: <kbd>></kbd>
|
||||
|
||||
* **Forward message**: <kbd><</kbd>
|
||||
|
||||
* **Reply directly to sender**: <kbd>Shift</kbd> + <kbd>R</kbd>
|
||||
|
||||
* **Reply @-mentioning sender**: <kbd>@</kbd>
|
||||
|
||||
### In the compose box
|
||||
@@ -146,7 +104,6 @@ in the Zulip app to add more to your repertoire as needed.
|
||||
* **Send message**: <kbd>Tab</kbd> then <kbd>Enter</kbd>, or either
|
||||
<kbd>Enter</kbd> or <kbd>Ctrl</kbd> + <kbd>Enter</kbd> based on
|
||||
[your settings][toggle-enter-to-send]
|
||||
|
||||
* **Insert new line**: <kbd>Shift</kbd> + <kbd>Enter</kbd>, or either
|
||||
<kbd>Enter</kbd> or <kbd>Ctrl</kbd> + <kbd>Enter</kbd> based on
|
||||
[your settings][toggle-enter-to-send]
|
||||
@@ -154,17 +111,12 @@ in the Zulip app to add more to your repertoire as needed.
|
||||
[toggle-enter-to-send]: /help/configure-send-message-keys
|
||||
|
||||
* **Insert italic text**: `*italic*` or <kbd>Ctrl</kbd> + <kbd>I</kbd>
|
||||
|
||||
* **Insert bold text**: `**bold**` or <kbd>Ctrl</kbd> + <kbd>B</kbd>
|
||||
|
||||
* **Insert link**: `[Zulip website](https://zulip.org)` or <kbd>Ctrl</kbd> +
|
||||
<kbd>Shift</kbd> + <kbd>L</kbd>
|
||||
|
||||
* **Insert or create a [saved snippet](/help/saved-snippets)**:
|
||||
<kbd>Ctrl</kbd> + <kbd>'</kbd>
|
||||
|
||||
* **Toggle preview mode**: <kbd>Alt</kbd> + <kbd>P</kbd>
|
||||
|
||||
* **Cancel compose and save draft**: <kbd>Esc</kbd> or
|
||||
<kbd data-mac-key="Ctrl">Ctrl</kbd> + <kbd>[</kbd> — Close the compose box
|
||||
and save the unsent message as a draft.
|
||||
@@ -178,30 +130,19 @@ in the Zulip app to add more to your repertoire as needed.
|
||||
### For a selected message (outlined in blue)
|
||||
|
||||
* **Edit message or view original message**: <kbd>E</kbd>
|
||||
|
||||
* **Show message sender's user card**: <kbd>U</kbd>
|
||||
|
||||
* **View read receipts**: <kbd>Shift</kbd> + <kbd>V</kbd> — Same shortcut
|
||||
also closes the read receipts menu (if open).
|
||||
|
||||
* **View image**: <kbd>V</kbd>
|
||||
|
||||
* **Move message and (optionally) other messages in the same topic**: <kbd>M</kbd>
|
||||
|
||||
* **View message edit and move history**: <kbd>Shift</kbd> +
|
||||
<kbd>H</kbd>. Viewing message edit history [must be
|
||||
allowed](/help/restrict-message-edit-history-access).
|
||||
|
||||
* **Star message**: <kbd>Ctrl</kbd> + <kbd>S</kbd>
|
||||
|
||||
* **React with 👍**: <kbd>+</kbd>
|
||||
|
||||
* **Toggle first emoji reaction**: <kbd>=</kbd>
|
||||
|
||||
* **Mark as unread from selected message**: <kbd>Shift</kbd> + <kbd>U</kbd>
|
||||
|
||||
* **Collapse/show message**: <kbd>-</kbd>
|
||||
|
||||
* **Toggle topic mute**: <kbd>Shift</kbd> + <kbd>M</kbd>. This works in both
|
||||
message views and views that list topics (e.g., [inbox](/help/inbox), [recent
|
||||
conversations](/help/recent-conversations)). Learn about [muted
|
||||
@@ -210,11 +151,8 @@ in the Zulip app to add more to your repertoire as needed.
|
||||
## Recent conversations
|
||||
|
||||
* **View recent conversations**: <kbd>T</kbd>
|
||||
|
||||
* **Search recent conversations**: <kbd>T</kbd>
|
||||
|
||||
* **Escape from recent conversations search**: <kbd>Esc</kbd> or arrow keys
|
||||
|
||||
* **Navigate recent conversations**: Use arrow keys or vim keys
|
||||
(<kbd>J</kbd>, <kbd>K</kbd>, <kbd>L</kbd>, <kbd>H</kbd>).
|
||||
|
||||
@@ -227,7 +165,6 @@ Use <kbd>Enter</kbd> to engage with elements.
|
||||
### Within the drafts view
|
||||
|
||||
* **Edit selected draft**: <kbd>Enter</kbd>
|
||||
|
||||
* **Delete selected draft**: <kbd>Backspace</kbd>
|
||||
|
||||
Keyboard navigation (e.g., arrow keys) works as expected.
|
||||
@@ -235,17 +172,13 @@ Keyboard navigation (e.g., arrow keys) works as expected.
|
||||
## Menus
|
||||
|
||||
* **Toggle shortcuts help**: <kbd>?</kbd>
|
||||
|
||||
* **Toggle gear menu**: <kbd>G</kbd>
|
||||
|
||||
* **Open personal menu**: <kbd>G</kbd> + <kbd class="arrow-key">→</kbd>
|
||||
|
||||
* **Open help menu**: <kbd>G</kbd> + <kbd class="arrow-key">←</kbd>
|
||||
|
||||
### For a selected message (outlined in blue)
|
||||
|
||||
* **Toggle emoji reactions menu**: <kbd>:</kbd>
|
||||
|
||||
* **Toggle message actions menu**: <kbd>I</kbd>
|
||||
|
||||
## Channel settings
|
||||
@@ -257,17 +190,14 @@ Keyboard navigation (e.g., arrow keys) works as expected.
|
||||
|
||||
Pressing <kbd class="arrow-key">↑</kbd> from the first channel
|
||||
in the list moves you to the **Filter channels** input.
|
||||
|
||||
* **Switch between tabs**: <kbd class="arrow-key">←</kbd> and
|
||||
<kbd class="arrow-key">→</kbd> — Switch between the **Subscribed**
|
||||
and **All channels** tabs.
|
||||
|
||||
* **Create new channel**: <kbd>N</kbd>
|
||||
|
||||
### For a selected channel
|
||||
|
||||
* **View channel messages**: <kbd>Shift</kbd> + <kbd>V</kbd>
|
||||
|
||||
* **Toggle subscription**: <kbd>Shift</kbd> + <kbd>S</kbd>
|
||||
|
||||
|
||||
|
||||
@@ -79,7 +79,6 @@ In addition, links to messages, topics, and channels are **permanent**:
|
||||
or [channel](/help/move-content-to-another-channel), or if its [topic is
|
||||
resolved](/help/resolve-a-topic). Zulip uses the same permanent link syntax
|
||||
when [quoting a message](/help/quote-or-forward-a-message).
|
||||
|
||||
- [Topic links](#get-a-link-to-a-specific-topic) will still work even when the
|
||||
topic is [renamed](/help/rename-a-topic), [moved to another
|
||||
channel](/help/move-content-to-another-channel), or
|
||||
|
||||
@@ -26,16 +26,13 @@ Here are some ways to find the URL for your Zulip organization.
|
||||
accounts**](https://zulip.com/accounts/find/) page and enter the email address
|
||||
that you signed up with. You will receive an email with the sign-in
|
||||
information for any Zulip organizations associated with your email address.
|
||||
|
||||
* Search your email account for a registration email from Zulip. The subject
|
||||
line will include `Zulip: Your new account details` or `Zulip: Your new
|
||||
organization details`. This email provides your organization's log in URL.
|
||||
|
||||
* If you have visited your organization's log in page in the past, try reviewing
|
||||
your browser's history. Searching for `zulipchat.com` should find the right
|
||||
page if your Zulip organization is hosted on [Zulip
|
||||
Cloud](https://zulip.com/plans/).
|
||||
|
||||
* You can ask your organization administrators for your Zulip URL.
|
||||
|
||||
{tab|logged-in}
|
||||
@@ -43,16 +40,13 @@ Here are some ways to find the URL for your Zulip organization.
|
||||
* If using Zulip in the browser, your organization's Zulip log in URL is the first part
|
||||
of what you see in the URL bar (e.g., `<organization-name>.zulipchat.com` for
|
||||
[Zulip Cloud](https://zulip.com/plans/) organizations).
|
||||
|
||||
* In the Desktop app, select **Copy Zulip URL** from the **Zulip** menu to
|
||||
copy the URL of the currently active organization. You can also access the
|
||||
**Copy Zulip URL** option by right-clicking on an organization logo in the
|
||||
**organizations sidebar** on the left.
|
||||
|
||||
* In the Mobile app, tap your **profile picture** in the bottom right corner of
|
||||
the app, then tap **switch account** to see the URLs for all the organizations
|
||||
you are logged in to.
|
||||
|
||||
* On [Zulip Cloud](https://zulip.com/plans/) and other Zulip servers updated to
|
||||
[Zulip 6.0 or
|
||||
higher](https://zulip.readthedocs.io/en/stable/overview/changelog.html#zulip-6-x-series),
|
||||
|
||||
@@ -8,12 +8,10 @@ There are many ways to use this feature, including:
|
||||
|
||||
- When you don't have time to read a conversation carefully, or to follow up on
|
||||
action items, mark messages as unread to return to them later.
|
||||
|
||||
- You can mark messages as unread when you [subscribe to a
|
||||
channel](/help/introduction-to-channels#browse-and-subscribe-to-channels). This makes it
|
||||
[convenient](/help/reading-strategies) to review all the recent
|
||||
conversations in that channel.
|
||||
|
||||
- Mark the results of your [search](/help/search-for-messages) as unread to
|
||||
review them at leisure.
|
||||
|
||||
|
||||
@@ -72,7 +72,6 @@ Users can disable notifications for `@**topic**` mentions by:
|
||||
- Disabling notifications for wildcard mentions
|
||||
[globally](/help/dm-mention-alert-notifications) or for [individual
|
||||
channels](/help/channel-notifications).
|
||||
|
||||
- Muting the [topic](/help/mute-a-topic) or [channel](/help/mute-a-channel).
|
||||
|
||||
## Mention everyone on a channel
|
||||
@@ -89,7 +88,6 @@ Users can disable notifications for `@**all**`, `@**everyone**`, and
|
||||
- Disabling notifications for wildcard mentions
|
||||
[globally](/help/dm-mention-alert-notifications) or for [individual
|
||||
channels](/help/channel-notifications).
|
||||
|
||||
- Muting the [topic](/help/mute-a-topic) or [channel](/help/mute-a-channel).
|
||||
|
||||
## Examples
|
||||
|
||||
@@ -10,9 +10,7 @@
|
||||
You can send emails to Zulip channels. This can be useful:
|
||||
|
||||
* If you have an email that you want to discuss on Zulip
|
||||
|
||||
* For mirroring mailing list traffic
|
||||
|
||||
* For integrating a third-party app that can send emails, but which does not
|
||||
easily lend itself to a more direct integration
|
||||
|
||||
@@ -64,15 +62,12 @@ Zulip message.
|
||||
|
||||
* **The sender's email address**: Adds `From: <Sender email address>` to
|
||||
the top of the Zulip message.
|
||||
|
||||
* **Email footers**: By default, Zulip tries to automatically remove some footer
|
||||
text (like signatures). With this option enabled, Zulip will include all footers.
|
||||
|
||||
* **Quoted original email**: In many email clients, when you reply to a message
|
||||
(e.g., a message notification email), a copy of the original message is
|
||||
automatically added to the bottom of your reply. By default, Zulip tries
|
||||
to remove that copied message. With this option enabled, Zulip will include it.
|
||||
|
||||
* **Use html encoding**: The body of an email is typically encoded using
|
||||
one or both of two common formats: plain text (`text/plain`) and
|
||||
HTML (`text/html`). Zulip supports constructing the Zulip message
|
||||
|
||||
@@ -60,7 +60,6 @@ Standard hosting.
|
||||
|
||||
* Retention policies are processed in a daily job; so changes in the
|
||||
policy won't have any effect until the next time the daily job runs.
|
||||
|
||||
* Deleted messages are preserved temporarily in a special archive. So
|
||||
if you discover a misconfiguration accidentally deleted content you
|
||||
meant to preserve, contact Zulip support promptly for assistance with
|
||||
|
||||
@@ -77,5 +77,4 @@ channels](/help/search-for-messages#search-by-location).
|
||||
## Related articles
|
||||
|
||||
* [Mute or unmute a topic](/help/mute-a-topic)
|
||||
|
||||
* [Mute a user](/help/mute-a-user)
|
||||
|
||||
@@ -11,32 +11,25 @@ have the following effects:
|
||||
* Combined feed sent by a muted user will automatically be [marked as
|
||||
read](/help/marking-messages-as-read) for you, and will never
|
||||
generate any desktop, email, or mobile push notifications.
|
||||
|
||||
* Combined feed sent by muted users, including the name, profile
|
||||
picture, and message content, are hidden behind a **Click here to
|
||||
reveal** banner. A revealed message can later be [re-hidden](/help/mute-a-user#re-hide-a-message-that-has-been-revealed).
|
||||
|
||||
* Muted users are hidden from [**Direct
|
||||
messages**](/help/direct-messages) in the left sidebar and the list
|
||||
of users in the right sidebar. Direct messages between you and a
|
||||
muted user are excluded from all views, including search, unless you
|
||||
[explicitly search](/help/search-for-messages) for `dm-with:<that
|
||||
user>`.
|
||||
|
||||
* Muted users have their name displayed as "Muted user" for [emoji
|
||||
reactions][view-emoji-reactions], [polls](/help/create-a-poll), and
|
||||
when displaying the recipients of group direct messages.
|
||||
|
||||
* Muted users are excluded from the autocomplete for composing a
|
||||
direct message or [mentioning a user](/help/mention-a-user-or-group).
|
||||
|
||||
* Muted users are excluded from [read receipts](/help/read-receipts)
|
||||
for all messages. Zulip never shares whether or not you have read
|
||||
a message with a user you've muted.
|
||||
|
||||
* **Recent conversations** and other features that display avatars will
|
||||
show a generic user symbol in place of a muted user's profile picture.
|
||||
|
||||
* To avoid interfering with administration tasks, channel and
|
||||
organization settings display muted users' names and other details.
|
||||
|
||||
|
||||
@@ -6,7 +6,6 @@ space for the message feed. There are a number of ways to open the compose box.
|
||||
## Using the mouse
|
||||
|
||||
* Click on any message.
|
||||
|
||||
* Click on **Start new conversation**, or **New direct message** at the
|
||||
bottom of the app.
|
||||
|
||||
@@ -15,9 +14,7 @@ space for the message feed. There are a number of ways to open the compose box.
|
||||
All replies are to the message in the **blue box**.
|
||||
|
||||
* **Reply**: <kbd>R</kbd> or <kbd>Enter</kbd>
|
||||
|
||||
* **New topic**: <kbd>C</kbd>
|
||||
|
||||
* **New direct message**: <kbd>X</kbd>
|
||||
|
||||
You can move the blue box around using the **arrow keys**, <kbd>J</kbd>, or
|
||||
|
||||
@@ -15,7 +15,6 @@ account and how users access their accounts:
|
||||
* You can [require an invitation](#set-whether-invitations-are-required-to-join)
|
||||
to sign up (default), or you can [allow anyone to
|
||||
join](#set-whether-invitations-are-required-to-join) without an invitation.
|
||||
|
||||
* You can [restrict the ability to invite new
|
||||
users](#change-who-can-send-invitations) to any combination of
|
||||
[roles](/help/user-roles), [groups](/help/user-groups), and individual
|
||||
@@ -25,12 +24,10 @@ Regardless of whether invitations are required, you can:
|
||||
|
||||
* [Configure allowed authentication
|
||||
methods](/help/configure-authentication-methods).
|
||||
|
||||
* [Restrict sign-ups to a fixed list of allowed
|
||||
domains](#restrict-sign-ups-to-a-list-of-domains)
|
||||
(including subdomains). For example, you can require users to sign up with
|
||||
the email domain for your business or university.
|
||||
|
||||
* Disallow signups with known [disposable email
|
||||
address](https://en.wikipedia.org/wiki/Disposable_email_address). This
|
||||
is recommended for open organizations to help protect against abuse.
|
||||
|
||||
@@ -27,21 +27,17 @@ options:
|
||||
|
||||
- **Free**: Includes free access to Zulip's [Mobile Push Notification
|
||||
Service][push-notifications] for up to 10 users.
|
||||
|
||||
- **Basic**: Includes unlimited access to Zulip's [Mobile Push Notification
|
||||
Service][push-notifications] for organizations with more than 10 users.
|
||||
|
||||
- **Business**: Includes commercial support, in addition to push notifications
|
||||
access. Zulip's support team can answer questions about installation and
|
||||
upgrades, provide guidance in tricky situations, and help avoid painful
|
||||
complications before they happen. You can also get guidance on how best to use
|
||||
dozens of Zulip features and configuration options.
|
||||
|
||||
- **Enterprise**: If your organization requires hands-on support, such as
|
||||
real-time assistance during installation and upgrades, help with advanced
|
||||
deployment options, development of custom features or integrations, etc.,
|
||||
please contact [sales@zulip.com](mailto:sales@zulip.com) to discuss pricing.
|
||||
|
||||
- **Community**: This free plan includes unlimited push notifications access,
|
||||
and is available for many non-commercial organizations with more than 10 users
|
||||
(details [below](#free-community-plan)).
|
||||
@@ -152,7 +148,6 @@ An organization is considered to be a new customer if:
|
||||
|
||||
- It was not registered for Zulip's [Mobile Push Notification
|
||||
Service][push-notifications] prior to December 12, 2023, and
|
||||
|
||||
- It has never previously signed up for a self-hosted Zulip plan (Basic,
|
||||
Business, Community or Enterprise).
|
||||
|
||||
@@ -318,9 +313,7 @@ large organization.
|
||||
|
||||
- [Education organizations](#education-pricing) and [non-profit
|
||||
organizations](#non-profit-pricing).
|
||||
|
||||
- Discounts are available for organizations based in the **developing world**.
|
||||
|
||||
- Any organization where many users are **not paid staff** is likely eligible
|
||||
for a discount.
|
||||
|
||||
@@ -342,7 +335,6 @@ university IT) may qualify for [non-profit pricing](#non-profit-pricing).
|
||||
- **Basic plan**: $0.50 per user per month
|
||||
- **Business plan**: $1 per user per month with annual billing
|
||||
($1.20/month billed monthly) with a minimum purchase of 100 licenses.
|
||||
|
||||
- **Non-profit education pricing**: The non-profit discount applies to
|
||||
online purchases only (no additional legal agreements) for use at registered
|
||||
non-profit institutions (e.g., colleges and universities).
|
||||
|
||||
@@ -81,7 +81,6 @@ There are a few ways to set up Zulip, and different ones may be convenient for y
|
||||
- Students and staff can use a single Zulip account for all classes.
|
||||
- You can create department-wide channels, e.g., for announcing talks or other events.
|
||||
- You don’t need to set up a separate server if you’re self-hosting Zulip.
|
||||
|
||||
* You can **set up a separate Zulip organization for each class**
|
||||
you’re teaching. Advantages:
|
||||
- This makes it simple to manage permissions, e.g., if you want to
|
||||
@@ -90,8 +89,6 @@ There are a few ways to set up Zulip, and different ones may be convenient for y
|
||||
- Students can’t see who is in channels for other classes.
|
||||
- You can easily switch between multiple Zulip organizations in
|
||||
the [Zulip desktop apps](/apps/).
|
||||
|
||||
|
||||
* You can **use a single Zulip organization for several classes**
|
||||
you’re teaching, perhaps re-purposing a Zulip organization from a
|
||||
prior term. Advantages:
|
||||
@@ -125,11 +122,9 @@ A few settings to highlight:
|
||||
* If your class uses a programming language, set the [default
|
||||
language for code blocks][default-code-block-language]. Also
|
||||
consider setting up [code playgrounds][code-playgrounds].
|
||||
|
||||
* If your class uses code repositories, [set up
|
||||
linkifiers](/help/add-a-custom-linkifier) to make it easy to link to
|
||||
issues (e.g., just by typing #1234 for issue 1234).
|
||||
|
||||
* [Add custom emoji](/help/custom-emoji) that your class will enjoy.
|
||||
|
||||
[default-code-block-language]: /help/code-blocks#default-code-block-language
|
||||
|
||||
@@ -121,11 +121,9 @@ There are three availability states:
|
||||
* **Active** (<span class="user-circle user-circle-active zulip-icon
|
||||
zulip-icon-user-circle-active"></span>): Zulip is open and in focus on web,
|
||||
desktop or mobile, or was in the last 140 seconds.
|
||||
|
||||
* **Idle** (<span class="user-circle user-circle-idle zulip-icon
|
||||
zulip-icon-user-circle-idle"></span>): Zulip is open on your computer (either
|
||||
desktop or web), but you are not active.
|
||||
|
||||
* **Offline** (<span class="user-circle user-circle-offline zulip-icon
|
||||
zulip-icon-user-circle-offline"></span>): Zulip is not open on your computer,
|
||||
or you have turned on invisible mode.
|
||||
|
||||
@@ -11,7 +11,6 @@ time, but still make a big difference.
|
||||
helps fund free [Zulip Cloud Standard](https://zulip.com/plans/) hosting for
|
||||
hundreds of open source projects, research communities, and other worthy
|
||||
organizations.
|
||||
|
||||
* [Help others find Zulip](#help-others-find-zulip): As a business that's
|
||||
[growing sustainably](https://zulip.com/values/) without venture capital
|
||||
funding, Zulip cannot afford splashy ad campaigns to compete with giant
|
||||
@@ -19,7 +18,6 @@ time, but still make a big difference.
|
||||
on users and other members of the community to spread the word about the
|
||||
difference that using Zulip's organized team chat has made for you or your
|
||||
organization.
|
||||
|
||||
* [Help improve Zulip](#help-improve-zulip): Zulip is developed by a [vibrant
|
||||
open-source community](https://zulip.com/team/), and there are many ways to
|
||||
contribute even without writing a single line of code.
|
||||
@@ -36,35 +34,28 @@ Collective](https://opencollective.com/zulip).
|
||||
* [**Link to Zulip**](/help/linking-to-zulip-website) from your organization's
|
||||
website. In addition to providing information for anyone browsing your
|
||||
website, this helps people find Zulip in Google and other search engines.
|
||||
|
||||
* [**List your organization**](/help/communities-directory) in the [Zulip
|
||||
communities directory](https://zulip.com/communities/). Browsing open
|
||||
communities helps folks see how others are using Zulip, and learn best
|
||||
practices.
|
||||
|
||||
* **Star** Zulip on GitHub. There are four main repositories:
|
||||
[server/web](https://github.com/zulip/zulip),
|
||||
[mobile](https://github.com/zulip/zulip-mobile),
|
||||
[desktop](https://github.com/zulip/zulip-desktop), and
|
||||
[Python API](https://github.com/zulip/python-zulip-api).
|
||||
|
||||
* **Review** Zulip on product comparison websites, such as
|
||||
[G2](https://www.g2.com/products/zulip/reviews/start) and [Software
|
||||
Advice](https://reviews.softwareadvice.com/new/316022). Organizations rely on
|
||||
review sites more and more when choosing software for their team, and sharing
|
||||
your experience with Zulip (good or bad) helps them evaluate whether Zulip
|
||||
might work for their needs.
|
||||
|
||||
* **Subscribe** to [our blog](https://blog.zulip.org/), and share our posts.
|
||||
|
||||
* **Mention** Zulip on social media, or like and retweet [Zulip's
|
||||
tweets](https://twitter.com/zulip), or retoot [Zulip's
|
||||
toots](https://fosstodon.org/@zulip).
|
||||
|
||||
* **Share** your Zulip story on your blog, or get it posted [on the Zulip
|
||||
website](https://zulip.com/use-cases/#customer-stories) (contact
|
||||
[support@zulip.com](mailto:support@zulip.com) to learn more).
|
||||
|
||||
* **Tell** your friends and colleagues about your Zulip experience.
|
||||
|
||||
## Help improve Zulip
|
||||
@@ -74,17 +65,14 @@ Collective](https://opencollective.com/zulip).
|
||||
and [bug
|
||||
reports](https://zulip.readthedocs.io/en/latest/contributing/reporting-bugs.html).
|
||||
Many improvements to the Zulip app start with a user's suggestion.
|
||||
|
||||
* [**Give
|
||||
feedback**](https://zulip.readthedocs.io/en/latest/contributing/suggesting-features.html#evaluation-and-onboarding-feedback)
|
||||
if you are evaluating or using Zulip.
|
||||
|
||||
* [**Translate**](https://zulip.readthedocs.io/en/latest/translating/translating.html)
|
||||
Zulip into your language. Zulip has been translated into over 25 languages by
|
||||
an amazing group of volunteers, and you can help expand, improve, and
|
||||
maintain the translation for your language, or start working on a language
|
||||
that hasn't been covered yet.
|
||||
|
||||
* [**Contribute
|
||||
code**](https://zulip.readthedocs.io/en/latest/contributing/contributing.html)
|
||||
to the Zulip open-source project. To make it easy for contributors from a
|
||||
|
||||
@@ -15,7 +15,6 @@ It's also easy to try out Zulip for yourself.
|
||||
where hundreds of participants collaborate to improve Zulip. Many parts of
|
||||
the community are open for [public access](/help/public-access-option), so
|
||||
you can start exploring without creating an account.
|
||||
|
||||
- [See how Zulip is being used](https://zulip.com/communities/) in open
|
||||
organizations that have opted in to be listed in the [Zulip communities
|
||||
directory](/help/communities-directory).
|
||||
@@ -34,15 +33,12 @@ It's also easy to try out Zulip for yourself.
|
||||
- Customize [organization settings](/help/customize-organization-settings)
|
||||
and [settings for new users](/help/customize-settings-for-new-users), but
|
||||
plan to adjust the details as you go.
|
||||
|
||||
- [Create](/help/create-channels) your initial
|
||||
[channels](/help/introduction-to-channels), including a dedicated channel for
|
||||
questions and feedback about using Zulip.
|
||||
|
||||
- Educate others about how to use Zulip's [topics](/help/introduction-to-topics),
|
||||
and how to [move](/help/move-content-to-another-topic) any messages that
|
||||
belong elsewhere.
|
||||
|
||||
- [Set up integrations](/help/set-up-integrations) so that your team can
|
||||
experience all their regular workflows inside the Zulip app.
|
||||
|
||||
|
||||
@@ -9,27 +9,22 @@ You can also manage permissions with [custom user groups](/help/user-groups).
|
||||
* **Organization owner**: Can manage users, public channels, organization
|
||||
settings, and billing. Organization owners can do anything that an
|
||||
organization administrator can do.
|
||||
|
||||
* **Organization administrator**: Can manage users, public channels, and
|
||||
organization settings. Cannot make someone an owner, or change an existing
|
||||
owner's role.
|
||||
|
||||
* **Moderator**: Can do anything that members can do, plus additional
|
||||
permissions [configured](/help/manage-permissions) by
|
||||
your organization.
|
||||
|
||||
* **Member**: This is the default role for most users. Members have access to
|
||||
all public channels. You can [configure different
|
||||
permissions](/help/restrict-permissions-of-new-members) for **new members**
|
||||
and **full members**, which is especially useful for [moderating open
|
||||
organizations](/help/moderating-open-organizations). New members automatically
|
||||
become full members after a configurable waiting period.
|
||||
|
||||
* **Guest**: Can view and send messages in channels they have been subscribed to.
|
||||
Guests cannot see other channels, unless they have been specifically subscribed
|
||||
to the channel. See [guest users documentation](/help/guest-users) for additional
|
||||
details and configuration options.
|
||||
|
||||
* **Billing administrator**: The user who upgrades the organization to
|
||||
a paid plan is, in addition to their normal role, a billing
|
||||
administrator. Billing administrators can manage billing for the organization.
|
||||
|
||||
@@ -17,13 +17,9 @@ attached to messages in your current view.
|
||||
1. You can interact with the image.
|
||||
|
||||
* Zoom in and out of the image
|
||||
|
||||
* Click and drag the image
|
||||
|
||||
* **Reset zoom** so that the image is recentered and back to its original size
|
||||
|
||||
* **Open** the image in a new browser tab
|
||||
|
||||
* **Download** the image
|
||||
|
||||
1. Click anywhere outside the image to close the image viewer once you are done.
|
||||
@@ -46,9 +42,7 @@ attached to messages in your current view.
|
||||
1. You can interact with the image.
|
||||
|
||||
* Zoom in and out of the image
|
||||
|
||||
* Pan the image if you are zoomed in
|
||||
|
||||
* Tap the **copy** (<i class="zulip-icon zulip-icon-copy mobile-help"></i>)
|
||||
icon in the bottom left corner of the app to copy a link to the image
|
||||
|
||||
@@ -68,17 +62,11 @@ attached to messages in your current view.
|
||||
1. You can interact with the video.
|
||||
|
||||
* **Play** the video
|
||||
|
||||
* Adjust the **volume**
|
||||
|
||||
* Watch in **full screen** mode
|
||||
|
||||
* **Open** the video in a new browser tab
|
||||
|
||||
* **Download** the video if it was uploaded to Zulip
|
||||
|
||||
* Adjust **playback speed**
|
||||
|
||||
* Turn on **picture-in-picture**
|
||||
|
||||
1. Click anywhere outside the video to close the video player once you are done.
|
||||
|
||||
@@ -80,9 +80,7 @@ discounts on **Zulip Cloud Standard**.
|
||||
|
||||
- Education organizations are eligible for [education
|
||||
pricing](https://zulip.com/for/education/#feature-pricing).
|
||||
|
||||
- Discounts are available for organizations based in the **developing world**.
|
||||
|
||||
- Non-profits and other organizations where many users are **not paid staff**
|
||||
are generally eligible for a discount.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user