Improvements

Author: clicketyclackety

content/docs/concepts/_index.md

@@ -2,6 +2,7 @@
 title: Concepts
 type: docs
 prev: docs/
+next: concepts/changes/
 sidebar:
   open: true
 weight: 100

content/docs/concepts/changes.md

@@ -1,7 +1,8 @@
 ---
 title: Changes
 type: docs
-prev: docs/folder/
+prev: docs/concepts/
+next: ownership/
 weight: 1001
 ---
 

content/docs/concepts/ownership.md

@@ -1,9 +1,9 @@
 ---
 title: Ownership
 type: docs
-prev: docs/folder/
+prev: concepts/changes/
+next: concepts/release/
 weight: 1002
-draft: true
 ---
 
 There are currently two types of Ownership in Crash

content/docs/concepts/release.md

@@ -1,8 +1,8 @@
 ---
 title: Release
 type: docs
-prev: docs/folder/
-draft: true
+prev: ownership/
+next: shared-model/
 weight: 1003
 ---
 
@@ -14,7 +14,7 @@ weight: 1003
 If a Geometry Object is added to Rhino it will add itself to the Undo stack.
 Consider the following theoretical scenario.
 
-- User A creates a complex loft and is rimming it with other surfaces
+- User A creates a complex loft and is trimming it with other surfaces
 - User B creates a box
 - User A recieves User B's Box
 - If user A wants to undo a change to their work, they must also undo User B's box

content/docs/concepts/shared-model.md

@@ -1,7 +1,7 @@
 ---
 title: Shared Model
 type: docs
-prev: docs/folder/
+prev: release/
 draft: true
 weight: 1004
 ---

content/docs/leaving-a-model.md

@@ -2,7 +2,7 @@
 title: Leaving a Shared Model
 type: docs
 prev: installation
-next: docs/advanced/
+next: docs/users-panel/
 sidebar:
   open: true
 weight: 4

content/docs/plugins/_index.md

@@ -2,12 +2,17 @@
 title: Crash Plugins
 type: docs
 prev: advanced/
+next: assembly/
 sidebar:
   open: true
 weight: 200
 ---
 
-Crash allows for 3rd party plugins to extend and even entirely replace the default functionality.
+{{< callout type="warning" >}}
+The Crash plugin system is a work in progress and the API can and will change version to version. Please do not build any plugins you completely rely on.
+{{< /callout >}}
+
+Crash allows for 3rd party plugins to extend and even entirely replace the default functionality. The Crash plugin system is integrated into the yak package manager system within Rhino.
 
 {{< cards >}}
 {{< card link="https://github.com/crashcloud/CrashPluginExample" title="Plugin Example" icon="book-open" >}}

content/docs/plugins/assembly.md

@@ -7,3 +7,18 @@ weight: 2001
 ---
 
 The Crash Plugin must be built into an `.op` assembly. As some plugins are created for Rhino using C++ and Crash requires a separate DLL so that any Plugin can create a separate C# DLL to consume anything required. Whilst it might make sense for some plugins to include Crash inside their main plugin, I'd like to make Crash separate and available for every plugin. You should include these in your `.yak` package so that Crash can find them.
+
+### Yak package structure
+
+// TODO : Use File structure in Hextra
+
+- Debug
+  -- Manifest.yml
+  -- net7.0
+  --- MyRhinoPlugin.rhp
+  --- MyCrashPlugin.op
+  --- MyPluginLib.dll
+  -- net4.8
+  --- MyRhinoPlugin.rhp
+  --- MyCrashPlugin.op
+  --- MyPluginLib.dll

content/docs/plugins/changes.md

@@ -16,7 +16,7 @@ The Change Definition describes how the changes are drawn, if at all, how they a
 
 # Change Create Action
 
-Change Create Actions define the circumstances in which a Change is created. This could be a Box being moved, deleted, selected, or even a completely unique event in your Plugin!
+Change Create Actions define the circumstances in which a Change is created. This could be a Box being moved, deleted, selected, or even a completely unique event in your Plugin! This change is then captured and sent to the server.
 
 {{< cards >}}
 {{< card link="https://github.com/crashcloud/Crash/blob/main/src/Crash.Handlers/Plugins/IChangeCreateAction.cs" title="IChangeCreateAction.cs" icon="code" >}}

content/docs/plugins/events.md

@@ -1,7 +1,7 @@
 ---
 title: Events
 type: docs
-prev: docs/advanced/changes
+prev: plugins/changes
 weight: 2003
 ---