🐰 advice

Author: ewowi

docs/develop/development.md

@@ -12,36 +12,36 @@
 
 ## Create a branch
 
-* Want to make changes: fork the repo (see installation)and submit pull requests, see [creating-a-pull-request-from-a-fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork):
+* Want to make changes: fork the repo (see installation) and submit pull requests, see [creating-a-pull-request-from-a-fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork):
 
-    * Only branch from the main branch! Press Branches, press New Branch, give it a name e.g. background-script and press Create new Branch, click on background-script
+  * Only branch from the main branch! Press Branches, press New Branch, give it a name e.g. background-script and press Create new Branch, click on background-script
 
-      <img width="90" src="https://github.com/user-attachments/assets/588d0854-bac1-4b70-8931-ba6db4c94248" />
+    <img width="90" src="https://github.com/user-attachments/assets/588d0854-bac1-4b70-8931-ba6db4c94248" />
 
 ## Make changes
 
-### Front End (UI)
+### Front-end (UI)
 
 * interface folder
     * interface/src/routes/moonbase for MoonBase and MoonLight (modules)
 * see [Prepare for development](https://moonmodules.org/MoonLight/develop/installation/#prepare-for-development) about nodejs, npm install
 
-```
+```markdown
 npm install
 npm run dev
 ```
 
 * see [Troubleshooting](https://moonmodules.org/MoonLight/develop/installation/#troubleshooting) about WWWData.h
 
-### Back End (Server)
+### Back-end (Server)
 
 There are 3 levels to add functionality:
 
 * **Standard ESP32-Sveltekit code**, e.g. Connections, Wifi and System. MoonBase files is also made using standard sveltekit as example but contains a few components used in MoonLight modules. Might be rewriteen as MoonLight Module in the future.
-  * lib folder for Sveltekit back end
+  * lib folder for Sveltekit vack-end
   * Read the [ESP32 Sveltekit docs](https://moonmodules.org/MoonLight/esp32sveltekit/)
 * [MoonLight Modules](https://moonmodules.org/MoonLight/moonbase/modules/) e.g. Lights Control, Effects, Info, Channels. They are subclasses of Modules.h/cpp and implement setupDefinition, onUpdate and optional loop. New modules need to be defined in main.cpp and added to menu.svelte. All further UI is generated by Module.svelte.
-  * src folder for MoonBase and MoonLight back end
+  * src folder for MoonBase and MoonLight vack-end
 * **MoonLight Nodes**: the easiest and recommended way. See Effects.h, Layouts.h, Modifiers.h and Drivers.h for examples. They match closest WLED usermods. Each node has controls, a setup and a loop and can be switched on and off. For specific purposes hasOnLayout() and hasModifier() can return true.
   * src/MoonLight/nodes
 
@@ -50,7 +50,7 @@ There are 3 levels to add functionality:
 * Go to the file(s) you want to change press edit and make the changes. 
 * ☑️ and ➡️ to build and or upload
 * Changes made to the UI are not always visible in the browser, clear the browser cache to see latest UI (see [connect to MoonLight](https://moonmodules.org/MoonLight/gettingstarted/installation/#connect-moonlight)).
-* MoonLight uses clang-format for c/c++ code and prettier for Svelte, javascript etc. Format your code before submitting! (right click Format Document on each page you change)
+* MoonLight uses clang-format for c/c++ code and prettier for Svelte, javascript etc. Format your code before submitting! (right-click Format Document on each page you change)
 * Press Commit Changes..., enter a commit message and an extended description, Press Commit Changes
 
 ## Document your changes
@@ -88,7 +88,7 @@ See [Documentation](https://moonmodules.org/MoonLight/develop/documentation/)
 
 ### UI development server
 
-To ease the frontend development you can deploy the back end code on an ESP32 board and pass the websocket and REST API calls through the development server's proxy running on your computer.
+To ease the frontend development you can deploy the vack-end code on an ESP32 board and pass the websocket and REST API calls through the development server's proxy running on your computer.
 
 This very much speeds up UI development as no flashing to ESP32 is required to test updated UI. Svaing an UI file is enough to see the results!!!
 

docs/develop/installation.md

@@ -110,7 +110,7 @@ Before changing code, test if the current download of MoonLight is running fine.
 
 * If you are developing or updating existing MoonLight installations MoonLight might be outdated or not show up correctly in the browser or not even appear. Two reasons
 
-    * Sometimes the latest front end code is not generated yet (WWWData.h). This is how to set it right: 
+    * Sometimes the latest front-end code is not generated yet (WWWData.h). This is how to set it right: 
         * Open platformIO new terminal (>_)
         * touch ./interface/src/app.html so the build process will be triggered to create a new WWWData.h
         * build the project (✔) - if nodejs is not installed (yet) you will get errors. See troubleshooting

docs/develop/nodes.md

@@ -53,8 +53,8 @@ A node implements the following (overloaded) functions:
         * Regular patterns (CRGB as default but also others like Moving Head ...)
 
 * See [Modules](../modules)
-* Upon changing a pin, driver.init will rerun (FastLED.addLeds, PD and VD driver.init)
-* Uses ESPLiveScripts, see compileAndRun. compileAndRun is started when in Nodes a file.sc is choosen
+* Upon changing a pin, driver.init will rerun (FastLED.addLeds, Parallel LED Driver.init)
+* Uses ESPLiveScripts, see compileAndRun. compileAndRun is started when in Nodes a file.sc is chosen
     * To do: kill running scripts, e.g. when changing effects
 * [Nodes.h](https://github.com/MoonModules/MoonLight/blob/main/src/MoonLight/Nodes.cpp): class Node (constructor, destructor, setup, loop, hasFunctions, map, modify, addControl(s), onUpdate)
 * [Nodes.cpp](https://github.com/MoonModules/MoonLight/blob/main/src/MoonLight/Nodes.cpp): implement LiveScriptNode
@@ -106,7 +106,7 @@ This is the current list of supported lights ranging from 3 channels per light (
 * MHBeTopper19x15W-32 🐺: 32 channels moving head
 * MH19x15W-24: 24 channels moving heads
 
-Based on the choosen value, the channels per light and the offsets will be set e.g. for GRB: header->channelsPerLight = 3; header->offsetRed = 1; header->offsetGreen = 0; header->offsetBlue = 2;. Drivers should not make this mapping, the code calling drivers should do.
+Based on the chosen value, the channels per light and the offsets will be set e.g. for GRB: header->channelsPerLight = 3; header->offsetRed = 1; header->offsetGreen = 0; header->offsetBlue = 2;. Drivers should not make this mapping, the code calling drivers should do.
 
 The RGB and W offsets needs to be re-ordered and brightness corrected from the channel array. Not only Art-Net but  also a LEDs driver need to accept channel arrays with more then 4 channels per light. Eg GRB6 is a type of led curtain some of us have, which a Chinese manufacturer screwed up: 6 channels per light but only rgb is used, 3 channels do nothing
 

docs/develop/standardsguidelines.md

@@ -35,7 +35,7 @@ Github will pick up the changes so your PR stays up-to-date.
 
 > [!CAUTION]
 > Do not use "force-push" while your PR is open!
-> It has many subtle and unexpected consequences on our github reposistory.
+> It has many subtle and unexpected consequences on our github repository.
 > For example, we regularly lost review comments when the PR author force-pushes code changes. So, pretty please, do not force-push.
 
 You can find a collection of very useful tips and tricks here: https://github.com/wled-dev/WLED/wiki/How-to-properly-submit-a-PR
@@ -62,7 +62,7 @@ You can find a collection of very useful tips and tricks here: https://github.co
 
 ### Code
 
-We use Clang-format for c-files (see .clang-format in the repo for the definition) and Prettier for front end files.
+We use Clang-format for c-files (see .clang-format in the repo for the definition) and Prettier for front-end files.
 
 Right click Format Document on each file you edit before committing.
 
@@ -72,7 +72,7 @@ Comments are used for technical documentation, always document your changes, eac
 (Functional documentation must be done on the MoonLight website, see above)
 
 Examples:  
-```
+```markdown
 // This is a comment.
 
 /* This is a CSS inline comment */

docs/develop/sveltekit.md

@@ -64,7 +64,7 @@ Below lists are ordered in terms of likelyhood to be accepted:
 
 ## Steps made to make Sveltekit ready for MoonLight
 
-This is a checklist, More info on most of the items can be found in the ESP32-Sveltekit specific documentation [ESP32 SvelteKit](https://moonmodules.org/MoonLight/esp32sveltekit/), [Build Tools](https://moonmodules.org/MoonLight/gettingstarted/), [Front end](https://moonmodules.org/MoonLight/sveltekit/) and [Back End](https://moonmodules.org/MoonLight/statefulservice/)
+This is a checklist, More info on most of the items can be found in the ESP32-Sveltekit specific documentation [ESP32 SvelteKit](https://moonmodules.org/MoonLight/esp32sveltekit/), [Build Tools](https://moonmodules.org/MoonLight/gettingstarted/), [Front-end](https://moonmodules.org/MoonLight/sveltekit/) and [Back-end](https://moonmodules.org/MoonLight/statefulservice/)
 
 * {custom} = MoonLight or name of a forked repo
 

docs/gettingstarted/overview.md

@@ -22,4 +22,4 @@ MoonLight documentation (this site) is organised as follows:
 * [Getting Started](https://moonmodules.org/MoonLight/gettingstarted/): Getting started with MoonLight
 * [MoonLight](https://moonmodules.org/MoonLight/moonlight/), [MoonBase](https://moonmodules.org/MoonLight/moonbase/), [Connections](https://moonmodules.org/MoonLight/connections/), [WiFi](https://moonmodules.org/MoonLight/wifi/), [System](https://moonmodules.org/MoonLight/system/status/): Help per module (MoonLight contains links to these pages)
 * [Develop](https://moonmodules.org/MoonLight/develop/): Info on developing for MoonLight
-* [ESP32 Sveltekit](https://moonmodules.org/MoonLight/esp32sveltekit/), [Build Tools](https://moonmodules.org/MoonLight/gettingstarted/), [Front End](https://moonmodules.org/MoonLight/sveltekit/), [Back End](https://moonmodules.org/MoonLight/statefulservice/): Information about the foundation of MoonLight, ESP32-Sveltekit, aimed at developers.
+* [ESP32 Sveltekit](https://moonmodules.org/MoonLight/esp32sveltekit/), [Build Tools](https://moonmodules.org/MoonLight/gettingstarted/), [Front-end](https://moonmodules.org/MoonLight/sveltekit/), [Back-end](https://moonmodules.org/MoonLight/statefulservice/): Information about the foundation of MoonLight, ESP32-Sveltekit, aimed at developers.

docs/moonbase/devices.md

@@ -6,4 +6,4 @@ Shows which other MoonLight devices are connected to your local network.
 
 * Device name: name of this device (set the name in the [WiFi station module](https://moonmodules.org/MoonLight/network/sta/))
 * Devices: Devices found on the network
-    * Click on IP to jump to the device
+  * Click on IP to jump to the device

docs/moonbase/inputoutput.md

@@ -36,7 +36,7 @@ For each board the following presets are defined:
     * Button On/Off
   * Planned soon
     * Battery
-    * Relais brightness
+    * Relay brightness
     * DMX (in)
   * Planned later
     * I2S for microphone and line in

docs/moonlight/drivers.md

@@ -37,8 +37,8 @@ Want to add a Driver to MoonLight, see [develop](https://moonmodules.org/MoonLig
 | HUB75 Driver | <img width="100" src="https://github.com/user-attachments/assets/620f7c41-8078-4024-b2a0-39a7424f9678"/> | <img width="100" src="https://github.com/user-attachments/assets/4d386045-9526-4a5a-aa31-638058b31f32"/> | Drive HUB75 panels<br>Not implemented yet |
 | IR Driver 🆕🚧 | <img width="100" src="../../media/moonlight/IRDriver.jpeg"/> |  | Receive IR commands and [Lights Control](https://moonmodules.org/MoonLight/moonlight/lightscontrol/) |
 
-
-Virtual LED Driver: Driving max 120! outputs. E.g. 48 panels of 256 LEDs each run at 50-100 FPS using shift registers. Not implemented yet
+* The Parallel LED driver uses different hardware peripherals depending on the MCU type: ESP32-D0: I2S, ESP32-S3: LCD_CAM, ESP32-P4: Parallel IO (ParLIO).
+* Virtual LED Driver: Driving max 120! outputs (E.g. 48 panels of 256 LEDs each run at 50-100 FPS) using shift registers. Integrated within the Parallel LED Driver architecture. Not implemented yet
 <img width="100" src="https://github.com/user-attachments/assets/98fb5010-7192-44db-a5c9-09602681ee15"/><img width="100" src="https://github.com/user-attachments/assets/c81d2f56-00d1-4424-a716-8e3c30e76636"/>
 
 ### Max Power and Light Preset

interface/src/lib/components/moonbase/MultiRow.svelte

@@ -143,7 +143,7 @@
 <div class="h-16 flex w-full items-center justify-between space-x-3 p-0 text-xl font-medium">
 	{initCap(property.name)}
 </div>
-{#if findItemInDefinition.crud == null || findItemInDefinition.crud.includes('c')}
+{#if findItemInDefinition?.crud == null || findItemInDefinition.crud.includes('c')}
 	<div class="relative w-full overflow-visible">
 		<!-- <div class="mx-4 mb-4 flex flex-wrap justify-end gap-2"> -->
 		<button
@@ -162,7 +162,7 @@
 {/if}
 
 <!-- Search Filter -->
-{#if findItemInDefinition.filter != null}
+{#if findItemInDefinition?.filter != null}
 	<MultiInput
 		property={propertyFilter}
 		bind:value={data[property.name + '_filter']}
@@ -184,12 +184,12 @@
 		items={filteredItems}
 		onReorder={handleReorder}
 		class="space-y-2"
-		dragDisabled={!(findItemInDefinition.crud == null || findItemInDefinition.crud.includes('s'))}
+		dragDisabled={!(findItemInDefinition?.crud == null || findItemInDefinition.crud.includes('s'))}
 	>
 		{#snippet children({ item: itemWrapper }: { item: any })}
 			<!-- svelte-ignore a11y_click_events_have_key_events -->
 			<div class="rounded-box bg-base-100 flex items-center space-x-3 px-4 py-2">
-				{#if findItemInDefinition.crud == null || findItemInDefinition.crud.includes('s')}
+				{#if findItemInDefinition?.crud == null || findItemInDefinition.crud.includes('s')}
 					<Grip class="h-6 w-6 text-base-content/30 cursor-grab flex-shrink-0" />
 				{/if}
 				<!-- Show the first 3 fields -->
@@ -226,7 +226,7 @@
 						>
 							<SearchIcon class="h-6 w-6" /></button
 						>
-						{#if findItemInDefinition.crud == null || findItemInDefinition.crud.includes('d')}
+						{#if findItemInDefinition?.crud == null || findItemInDefinition.crud.includes('d')}
 							<button
 								class="btn btn-ghost btn-sm"
 								onclick={() => {