Files
zulip/help/customize-organization-settings.md
Shubham Padia 7ce87c66ac 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.
2025-07-22 14:36:25 -07:00

37 lines
1.7 KiB
Markdown

# Customize organization settings
{!review-organization-settings-instructions.md!}
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
[topic][topic-editing-permissions] editing permissions, you can experience how
Zulip works for your organization before deciding what settings are best for
you.
[message-editing-permissions]: /help/restrict-message-editing-and-deletion
[topic-editing-permissions]: /help/restrict-moving-messages
[default-code-block-language]: /help/code-blocks#default-code-block-language
[code-playgrounds]: /help/code-blocks#code-playgrounds
[email-address-visibility]: /help/configure-email-visibility
[who-can-invite]: /help/restrict-account-creation#change-who-can-send-invitations
[who-can-join]: /help/restrict-account-creation#set-whether-invitations-are-required-to-join
## Related articles
* [Moving to Zulip](/help/moving-to-zulip)
* [Create your organization profile](/help/create-your-organization-profile)
* [Create channels](/help/create-channels)
* [Getting started with Zulip](/help/getting-started-with-zulip)