Slite Training
Instructions
This first section contains instructions for the admin / power user. Make sure to remove this section before running the training or sharing the doc with your team 
This doc is designed to help you create a training on Slite for your team. The doc takes you through all the different elements of our knowledge base. Using the "Duplicate" button in the upper right corner you can copy this doc over to your own workspace. You can pick and choose the elements that make sense for your team, and easily create a custom Slite training.
Some pro-tips:
- Focus on the basics, keep it simple and only go over the elements that people need to know. It's easy to overwhelm people that might not have that much experience with Slite.
- Where possible, use real use cases. This helps people to see how Slite fits in to their day to day.
- Repeat why you have picked Slite, why it is important, and what the benefit of using it is.
Questions? Feel free to email anouk@slite.com for additional support.
Slite 101 training
During this session, we'll cover the basics of Slite, and some best practices to help you make the most out of your knowledge base.
Agenda
- What makes a great doc?
- Let's create a doc together!
- Automating recurring processes
- Organising your knowledge base
- Find the information you need
- Keep your knowledge base up to date
- Q&A
What makes a great doc?
ABC
ABC - Audience Before Content. Consider the type of person who will be consuming your doc. What are their needs, and what do they care about?
Someone on your team might require a lot more detail versus someone from another part of the business that just wants the highlights (but does need more context).
Make it stand out
Nothing scares people as much as a wall of text. Make use of the different elements that Slite offers out of the box. You can use "/" to explore, and consider adding hints for summaries or sketches to explain more complex flows.
This sketch cannot currently be displayed in exports
Create a logical flow
The content of your doc should flow smoothly guiding the reader strategically through the content of your doc.
- Add an intro at the top of the doc,
- Use bullet points,
- Start with the most important information at the top,
- And have more detail in the body of the doc.
Use subheadings to break up content
Subheadings tell a story, they inform you the user in a matter of seconds what the doc is about. They break up the text and will be used if you add in a table of contents.
Headings (H1, H2, H3, H4) should be used to indicate the importance of a heading on the page. They should not be used stylistically to make text bigger or smaller.
Use the above-the-fold rule
Aim to make the main value point of your doc readable without the user having to scroll through the doc.
Let's create a doc together!
Let's create a doc together!
Automating recurring processes
Templates
Templates are perfect for any type of recurring doc. This could be weekly meetings, hiring scorecards, or designing new features. Templates can be managed from the template manager in the bottom left-hand of the sidebar.
Placeholders
Placeholders can be used in templates to indicate that content should be filled in. They're also a great way to instruct the writer about what sort of content needs to be added.
Create sub-docs automatically
You can automatically create new sub-docs based on a template and schedule.
Organizing your knowledge base
Writing great docs is only half of the battle. A great doc is useless if nobody knows how to find it. Organizing a knowledge base is an art. There's no golden rule on how to do it, however, there are some building blocks and best practices.
Similar to the ABC rule, you need to get clarity on your audience first. Who is going to use Slite, what will they use it for, and what are you hoping to achieve?
Some helpful resources:
This sketch cannot currently be displayed in exports
Channels
Channels are typically designed around a department, team, or project. Think of them like a folder for a selection of related documents that people would need access to as a whole.
Try to use a similar structure for the first layer of sub-docs in each channel.
Collections
Collections are similar to sub-docs, however, they come packed with a little extra 
Docs within a collection are displayed in a table. You can add any amount of columns to a collection with the same types that are available in standard tables.
This element (collection-block) isn't supported, or may require an update to be displayed. You can try to refresh the app.
Collection views
Collections can be filtered and sorted to tailor the collection to your needs. The configuration can be saved in a view so that you don't need to re-apply the same filters the next time you visit.
Find the information you need
Ask
Ask is our AI assistant, you can ask your knowledge base any question, as if you were tapping a colleague on the shoulder.
Ask is also available in Slack via our Slack integration!
Search (⌘K)
The Search (⌘K) menu is the easiest way to find docs in Slite.
Without any queries, the Search menu will also show you docs that you've recently edited and viewed.
Favouriting
Get easy access to the docs that are important to you by marking them as Favourites:
Updates
The updates page is a great place to start your Slite session. It shows you a combination of popular docs you might have missed, as well as updates in your favorite channels and your workspace in general.
Related Documents
Related Docs allows you to organically explore a certain topic within your workspace. You can find it when you hover over the header of a doc.
Keep your knowledge base up to date
A knowledge base is only as valuable as the content it holds. So make sure to utilize some of our features that can help to keep things up to date.
Doc verification
Make sure that you mark your most important docs as verified. This helps to:
.1Influence the search and Ask results
.2Your team to understand that this is information they can trust
.3To keep you accountable and check the content periodically
Knowledge Management Panel
Understand where your attention is needed, and how the knowledge base is being used by your team. Change the owner of multiple docs in one go, filter docs by channel to easily verify at a glance, and manage outdated docs by archiving in bulk.
Q&A
Any questions?
