 Slate is a monorepo divided up into multiple npm packages, so to install it you do You'll also need to be sure to install Slate's peer dependencies Note, if you'd rather use a pre-bundled version of Slate, you can and retrieve the bundled file!  Check out the guide for more information.

Installing Slate from Archbee

 Okay, so you've got Slate installed and rendered on the page, and when you type in it, you can see the changes reflected.  But you want to do more than just type a plaintext string.

Adding Event Handlers

 In our previous example, we started with a paragraph, but we never actually told Slate anything about the paragraph block type.  We just let it use its internal default renderer, which uses a plain old \<div> .

Defining Custom Elements

 In the previous guide we learned how to create custom block types that render chunks of text inside different containers.  But Slate allows for more than just "blocks".

Applying Custom Formatting

 Up until now, everything we've learned has been about how to write one-off logic for your specific Slate editor.  But one of the most powerful things about Slate is that it lets you model your specific rich text "domain" however you'd like, and write less one-off code.

Executing Commands

 Now that you've learned the basics of how to add functionality to the Slate editor, you might be wondering how you'd go about saving the content you've been editing, such that you can come back to your app later and have it load.  In this guide, we'll show you how to add logic to save your Slate content to a database for storage and retrieval later.

Saving to a Database

 For most folks, you'll want to install Slate via npm , in which case you can follow the regular guide.  But, if you'd rather install Slate by simply adding a \<script> tag to your application, this guide will help you.

Using the Bundled Source

Introduction to Slate!

Walkthroughs

Your documentation's source code where all files and their history are stored. The web editor connects to your documentation repository to access and modify content, or you can edit files locally in your preferred IDE.

repositoryyyyy

TestVASVariable

Are like departments for your users. You can create different groups (like Engineers, Marketing, or Management) and assign users to them. This helps you organize your users and give them different access levels to different parts of your organization

User_Groups

Connect multiple published Spaces for easy navigation between docs (e.g., User Guides, API docs). Add links in Space settings, label them, and publish. Changes to links automatically update across connected Spaces. 

Space_Links

Think of them as folders for your Spaces. You start with one called "Spaces." Make more folders if you need them. You can add, rename, or delete folders (but only if they're empty). To put a Space in a folder, just drag it there, use the move action,

Space_Group

Containers for documents organized by teams or projects. Each account has a personal space, and organizations can create custom ones with access control.

Spaces

Building blocks for your docs. Think of them as Legos for your content. You can use them to create headings, tables, images, code snippets, and more. There are basic, media, developer, and embedded blocks to choose from.

Blocks

dasdasdasdasdasda11

dsadasd3213dd

Glossary lets you define every tricky term, then gives them a sneak peek explanation on hover... Just like I'm doing with this text right here!

Glossary

variable_test_video

variable123

silviu

Bogdan_test

ferwhethgte

target1

google

test

support

product_name

specific

var_miha

new_var_2

new_mih_var

mih_var

This is a plain text that will be inserted in an expandable heading for using this raw as an exampl

testheight

available

testulet

testvar

altscenario

This is a plain text that will be inserted in an expandable heading for using this raw as an example