From 1d85a36f388ba06e3c73fb4a14c0bc438e319a51 Mon Sep 17 00:00:00 2001
From: Daniel Lautzenheiser <lautzd@gmail.com>
Date: Tue, 13 Dec 2022 16:15:41 -0500
Subject: [PATCH] doc: remove unsupported beta features

---
 core/dev-test/backends/github/config.yml |  2 +
 docs/content/docs/beta-features.mdx      | 81 +-----------------------
 2 files changed, 3 insertions(+), 80 deletions(-)

diff --git a/core/dev-test/backends/github/config.yml b/core/dev-test/backends/github/config.yml
index 21c1ef09..b9687de6 100644
--- a/core/dev-test/backends/github/config.yml
+++ b/core/dev-test/backends/github/config.yml
@@ -9,6 +9,8 @@ collections:
   - name: posts
     label: Posts
     label_singular: Post
+    media_folder: /assets/posts
+    public_folder: /assets/posts
     description: >
       The description is a great place for tone setting, high level information,
       and editing guidelines that are specific to a collection.
diff --git a/docs/content/docs/beta-features.mdx b/docs/content/docs/beta-features.mdx
index bb65ffdb..74ce07a7 100644
--- a/docs/content/docs/beta-features.mdx
+++ b/docs/content/docs/beta-features.mdx
@@ -18,7 +18,7 @@ Configuring the CMS for i18n support requires top level configuration, collectio
 ### Top level configuration
 
 <CodeTabs>
-  
+
 ```yaml
 i18n:
   # Required and can be one of multiple_folders, multiple_files or single_file
@@ -291,12 +291,6 @@ See [Folder Collections Path](/docs/collection-types#folder-collections-path).
 
 Seed [Nested Collections](/docs/collection-types#nested-collections).
 
-## Custom Mount Element
-
-Static CMS always creates its own DOM element for mounting the application, which means it always takes over the entire page, and is generally inflexible if you're trying to do something creative, like injecting it into a shared context.
-
-You can now provide your own element for Static CMS to mount in by setting the target element's ID as `nc-root`. If Static CMS finds an element with this ID during initialization, it will mount within that element instead of creating its own.
-
 ## Commit Message Templates
 
 You can customize the templates used by Static CMS to generate commit messages by setting the `commit_messages` option under `backend` in your Static CMS `config`.
@@ -445,76 +439,3 @@ CMS.registerEventListener({
   },
 });
 ```
-
-## Dynamic Default Values
-
-When linking to `/admin/#/collections/posts/new` you can pass URL parameters to pre-populate an entry.
-
-For example given the configuration:
-
-<CodeTabs>
-```yaml
-collections:
-  - name: posts
-    label: Posts
-    folder: content/posts
-    create: true
-    fields:
-      - label: Title
-        name: title
-        widget: string
-      - label: Object
-        name: object
-        widget: object
-        fields:
-          - label: Title
-            name: title
-            widget: string
-      - label: body
-        name: body
-        widget: markdown
-```
-
-```js
-collections: [
-  {
-    name: 'posts',
-    label: 'Posts',
-    folder: 'content/posts',
-    create: true,
-    fields: [
-      {
-        label: 'Title',
-        name: 'title',
-        widget: 'string'
-      },
-      {
-        label: 'Object',
-        name: 'object',
-        widget: 'object',
-        fields: [
-          {
-            label: 'Title',
-            name: 'title',
-            widget: 'string'
-          }
-        ],
-      },
-      {
-        label: 'body',
-        name: 'body',
-        widget: 'markdown'
-      },
-    ],
-  },
-],
-```
-
-</CodeTabs>
-
-clicking the following link: `/#/collections/posts/new?title=first&object.title=second&body=%23%20content`
-
-will open the editor for a new post with the `title` field populated with `first`, the nested `object.title` field
-with `second` and the markdown `body` field with `# content`.
-
-**Note:** URL Encoding might be required for certain values (e.g. in the previous example the value for `body` is URL encoded).