Updates documentation structure and content

.github/workflows/deploy.yaml

@@ -22,7 +22,7 @@ jobs:
       - uses: actions/checkout@v3
       - uses: actions/setup-node@v3
         with:
-          node-version: 18
+          node-version: 24
           cache-dependency-path: docs/yarn.lock
           cache: yarn
 

.github/workflows/test-deploy.yaml

@@ -20,7 +20,7 @@ jobs:
       - uses: actions/checkout@v3
       - uses: actions/setup-node@v3
         with:
-          node-version: 18
+          node-version: 24
           cache-dependency-path: docs/yarn.lock
           cache: yarn
 

docs/docs/HQ-guide/HQ-guide.mdx

@@ -1,7 +1,7 @@
 ---
 layout: default
 title: The Interactive & Immersive HQ
-sidebar_position: 3
+sidebar_position: 4
 ---
 
 import DocCardList from '@theme/DocCardList';

docs/docs/SM-guide/002-preference-settings.md

@@ -4,9 +4,9 @@ description: An overview of TouchDesigner preferences
 slug: /SM-guide/preferences
 ---
 
-# Recommended Preference Settings
+## Recommended Preference Settings
 
-Preferences is a dialog for setting personal default settings for various TouchDesigner options. These preferences are found in the Edit menu under Preferences.... These options are saved so they apply to your next TouchDesigner session. 
+Preferences is a dialog for setting personal default settings for various TouchDesigner options. These preferences are found in the Edit menu under Preferences.... These options are saved so they apply to your next TouchDesigner session.
 
 From the Edit menu select the Preferences dialog box. Alternatively, you could use the keyboard short-cut Alt + p
 
@@ -15,41 +15,45 @@ Here you’ll find a number of preferences for setting up your TouchDesigner env
 Alternatively, you can find the preference file located here:
 
 Platform | Path |
-:---      | :---  | 
+:---      | :---  |
 Windows  | `C:/Users/{username}/AppData/Local/Derivative/TouchDesigner/pref.txt`
 macOS    | `~Library/Application Support/Derivative/TouchDesigner</pref.txtcode>`
 
 ## Grid Snap
+
 By default the grid snap setting in TouchDesigner is set to course. Most of the networks you’ll find in our repos have been set with a fine network grid, which means if you re-arrange an operator, it will be difficult to find your way back into alignment with the project. For this reason, it’s worth changing your Snap to Grid to be fine.
 
 ## Resize
+
 For the sanity of other programmers, it’s well worth turning off the resize TOP and COMP checkboxes in your Network preferences tab. This keeps a uniform look to all TOPs and COMPs unless you choose to specifically deviate from the normal size.
 
 This is often an area of spirited discussion, and programmers often have very specific opinions about the right approach for sizing and network organization. That being said, it’s worth remembering that a formal structure to the choices made in sizing and placement help make a TouchDesigner network more readable and navigable. First starting with normed sizes allows the programmer to make specific choices, rather than arbitrary ones – a common byproduct of the use of auto resizing. for both TOPs and COMPs.
 
 Said another way, if the size and placement of your operators communicates meaning in your networks - then it's in your best intrest to make those decisiosn conscisouly.
 
 ## External Editors
+
 It’s often desirable to have an external editor for text and table elements in touch. Many of us use Sublime Text thought there are a wide variety of text editors that you might choose. External editors allow for syntax highlighting, and a variety of advanced features for speeding up the process of writing code. To set an external editor you need to use the DATs tab of the preferences window. Here you’ll find two fields where you can enter the paths to the executables for the applications you’d like to use.
 
 An example preference file:
 
 ```
-dats.texteditor	C:/Users/ragan/AppData/Local/Programs/Microsoft VS Code/Code.exe
-obj.adaptivehomedefault	0
-chops.graphdisplay2	6
-network.fitpaneltotile	0
-general.inc	0
-network.zoomdelay	0.19999999
-network.gridsnapdiv	2
-network.fittoptotile	0
-network.zoomboost	1.0000002
+dats.texteditor C:/Users/ragan/AppData/Local/Programs/Microsoft VS Code/Code.exe
+obj.adaptivehomedefault 0
+chops.graphdisplay2 6
+network.fitpaneltotile 0
+general.inc 0
+network.zoomdelay 0.19999999
+network.gridsnapdiv 2
+network.fittoptotile 0
+network.zoomboost 1.0000002
 ```
 
 ## Links to Derivative's official docs
+
 * [Preference Dialog]
 * [Preference Class]
 
 <!-- links -->
 [Preference Dialog]: https://docs.derivative.ca/Dialogs:Preferences_Dialog
-[Preference Class]:https://docs.derivative.ca/Preferences_Class
+[Preference Class]:https://docs.derivative.ca/Preferences_Class

docs/docs/SM-guide/004-network-organization.md

@@ -4,8 +4,6 @@ description: Organizing your thoughts and your noodles
 slug: /SM-guide/network-organization
 ---
 
-# Network Organization
-
 A network’s re-usability lives and dies in its organization and structuring. While there are limits to a modular approach, it’s well worth considering the larger implications around cultivating a forward focused temperament when building new systems. Every project will eventually come up against deadlines, changes orders, and the necessities of project delivery. To the best of our abilities, however, we might consider a tempered approach to thinking about how a particular element might be able to be used and re-used in future projects.
 
 To that end, clear organization and careful planning help facilitate this process. For the sake of a simple case study, let’s for a moment consider instancing networks. For the uninitiated, instancing allows you to reuse a single piece of geometry once it’s been passed to the GPU. This method of drawing geometry is significantly cheaper, computationally, than drawing additional copies of the geometry on the CPU. In principle, you only draw the geometry once, then create a transformation matrix for subsequent copies of the original geometry. The transformation of the copies is most efficiently done in CHOP channels, sometimes initially fed by a geometry converted to channel data.
@@ -25,8 +23,6 @@ If you’re not yet sold on this idea, at the very least consider dividing up yo
 * Limit the complexity of any given network – if you find a network is growing to be too sprawling, how might you re-organize or compartmentalize your implementation?
 * Think of your work in terms of a test against the other members of the team – would this structure and approach pass a Barry test? a Vlad test? a Bryant test?
 
-
-
 :::
 
 :::danger Don’t