diff --git a/docs/src/docPages/guide/collaborative-editing.md b/docs/src/docPages/guide/collaborative-editing.md
index 5e106ff7..33fefe8c 100644
--- a/docs/src/docPages/guide/collaborative-editing.md
+++ b/docs/src/docPages/guide/collaborative-editing.md
@@ -199,9 +199,14 @@ Yes, it’s magic. As already mentioned, that is all based on the fantastic Y.js
 ## Store the content
 Our collaborative editing backend is ready to handle advanced use cases, like authorization, persistence and scaling. Let’s go through a few common use cases here!
 
-:::pro Backend as a Service (Paid)
-Don’t want to wrap your head around the backend part? No worries, we offer a managed backend. For less than 1.000 documents, it’s $49/month (VAT may apply) and probably saves you a ton of time. Send us an email to [humans@tiptap.dev](mailto:humans@tiptap.dev) for further details.
+:::warning Work in progress
+Our plug & play collaboration backend hocuspocus is still work in progress. We’re setting up a dedicated website and documentation, and need to add one or two features before publishing it.
+
+If you want to give it a try, send us an email to humans@tiptap.dev to receive early access.
 :::
+<!-- :::pro Backend as a Service (Paid)
+Don’t want to wrap your head around the backend part? No worries, we offer a managed backend. For less than 1.000 documents, it’s $49/month (VAT may apply) and probably saves you a ton of time. Send us an email to [humans@tiptap.dev](mailto:humans@tiptap.dev) for further details.
+::: -->
 
 ### The document name
 The document name is `'example-document'` in all examples here, but it could be any string. In a real-world app you’d probably add the name of your entity, the ID of the entity and in some cases even the field (if you have multiple fields that you want to make collaborative). Here is how that could look like for a CMS:
diff --git a/docs/src/docPages/guide/node-views.md b/docs/src/docPages/guide/node-views.md
index 6c2f90ad..f4d864a6 100644
--- a/docs/src/docPages/guide/node-views.md
+++ b/docs/src/docPages/guide/node-views.md
@@ -30,6 +30,8 @@ TODO
 
 <demo name="Guide/NodeViews/TableOfContents" />
 
+<demo name="Examples/Drawing" />
+
 ### Advanced node views with content
 
 ```html
diff --git a/docs/src/docPages/overview/contributing.md b/docs/src/docPages/overview/contributing.md
index 05836280..bd35b8f1 100644
--- a/docs/src/docPages/overview/contributing.md
+++ b/docs/src/docPages/overview/contributing.md
@@ -12,6 +12,9 @@ tiptap would be nothing without its lively community. Contributions have always
 * New extensions, which don’t require changes to the core or other core extensions
 * Well explained, non-breaking changes to the core
 
+## Submit ideas
+Make sure to open an issue and outline your idea first. We’ll get back to you quickly and let you know if there is a chance we can merge your contribution.
+
 ## Set up the development environment
 It’s not too hard to tinker around with the offical repository. You’ll need [Git](https://github.com/git-guides/install-git), [Node](https://nodejs.org/en/download/) and [Yarn](https://classic.yarnpkg.com/en/docs/install/#mac-stable) installed. Here is what you need to do then:
 
diff --git a/docs/src/links.yaml b/docs/src/links.yaml
index 3136a90b..44c3b57d 100644
--- a/docs/src/links.yaml
+++ b/docs/src/links.yaml
@@ -49,7 +49,6 @@
       link: /guide/configuration
     - title: Create a toolbar
       link: /guide/toolbar
-      new: true
     - title: Custom styling
       link: /guide/styling
     - title: Store content
@@ -188,5 +187,5 @@
 
 - title: Links
   items:
-    - title: tiptap v1
+    - title: Documentation for tiptap 1.x
       link: https://v1.tiptap.dev