Community
Documents
Write your handbook, rules and SOPs where your staff already are, and share each one with exactly who should see it.
Documents is where your server writes for its staff. Everyone on the team can open it; the Resources permission manages everything in it.
Workspaces and folders
A server has up to 10 workspaces, each with folders (up to 3 deep) and documents (up to 1,000 in all). Drag a document or folder onto a folder to put it inside, or above or below a row to reorder; Move to… does the same from the keyboard. Deleting a folder moves what was in it up a level.
Sharing
Each workspace, folder and document can be shared with people, Discord roles, Jellyn roles, everyone on the team or management, each as a reader or an editor. A folder or document follows its folder by default, or has its own sharing.
With your team
With the link: anyone on your Jellyn team who has the link can read it, or edit it.
With your Discord server
With the link: anyone in your Discord server who has the link can read it, signed in with Discord, while they are in the server. Good for public rules.
Make a new link stops the old one working. Whoever wrote a document can always edit and share it.
Writing
The editor has menus (File, Edit, Insert, Help) and a ribbon for styles, fonts, colours, lists, alignment, links, pictures and tables. Type Markdown and it formats as you go:
| Type | Gets |
|---|---|
#, ## and a space | A heading |
- and a space | A list |
1. and a space | A numbered list |
> and a space | A quote |
| Three backticks | A code block |
/ on an empty line | What can be inserted: pictures, tables, a Discord invite, an ER:LC server card, a hint box |
It saves by itself a second after each change. If someone else saved in between, nothing is overwritten, and it says so.
Versions and history
- A version is kept when someone starts changing a document, and every 10 minutes while they do (the last 40). Put this version back keeps what was there as a version too.
- Who opened and changed it lists opens, edits, renames, moves and sharing changes.
Bringing in a GitBook
Export a GitBook space as Markdown and pick its .md files (up to 50 at once): each becomes a document, its first heading the title. GitBook's hints become hint boxes, and its tabs headings.
Documents are made safe on the server: no scripts, styles or pictures from other sites get through. Pictures are uploaded into the document (PNG, JPEG, GIF or WebP, up to 3 MB) and only shown to whoever may read it.