Update from equetzal/huronOS-build-tools@870dce8

huronOS · Aug 11, 2024 · d2d9979 · d2d9979
1 parent 7596c2f
commit d2d9979
Show file tree

Hide file tree

Showing 6 changed files with 428 additions and 2 deletions.
diff --git a/docs/assets/themed/dark/huronOS-desktop-enviroment.svg b/docs/assets/themed/dark/huronOS-desktop-enviroment.svg
diff --git a/docs/assets/themed/dark/system-modes.svg b/docs/assets/themed/dark/system-modes.svg
diff --git a/docs/assets/huronOS-desktop-enviroment.svg → ...emed/light/huronOS-desktop-enviroment.svg b/docs/assets/huronOS-desktop-enviroment.svg → ...emed/light/huronOS-desktop-enviroment.svg
diff --git a/docs/assets/system-modes.svg → docs/assets/themed/light/system-modes.svg b/docs/assets/system-modes.svg → docs/assets/themed/light/system-modes.svg
diff --git a/docs/introduction.md b/docs/introduction.md
@@ -8,7 +8,8 @@ sidebar_position: 1
 huronOS is designed to work as a **live USB** compatible with both legacy and UEFI BIOS, intended to **avoid the need to modify the hardware** provided by your educational institution; you only boot and **in a matter of seconds** you can have a **competitive programming environment** ready for a competition.
 
 ## Desktop Environment
-![huronOS' Desktop Environment](assets/huronOS-desktop-enviroment.svg)
+![huronOS' Desktop Environment](assets/themed/dark/huronOS-desktop-enviroment.svg#gh-dark-mode-only)
+![huronOS' Desktop Environment](assets/themed/light/huronOS-desktop-enviroment.svg#gh-light-mode-only)
 huronOS' desktop environment is **a first-of-its-kind**, being designed to only **keep what's important** for the contestants: Coding, Collaborating, and No Distractions.
 
 ## Synchronization 

diff --git a/docs/usage/directives/introduction-to-directives.md b/docs/usage/directives/introduction-to-directives.md
@@ -53,6 +53,7 @@ In event mode, the system has a separate partition disk (persistent) that stores
 
 To better understand modes and mode transitions, we use the following diagram to illustrate how *mode priorities* (Contest > Event > Default) are utilized to set up contests and events:
 
-![Mode Priorities](../../assets/system-modes.svg)
+![Mode Priorities](../../assets/themed/dark/system-modes.svg#gh-dark-mode-only)
+![Mode Priorities](../../assets/themed/light/system-modes.svg#gh-light-mode-only)
 
 In this example, you can see that the *default* mode is replaced with an event. This means that all data on the *default* persistence will be cleaned upon changing to the *event* mode, ensuring the event starts with a clean filesystem. Throughout the event, all data remains persistent between contests. The two contests are held within the contest time, and all contest data is copied to the event partition once the contest concludes. After the event, the filesystem is cleaned, and the *default* mode becomes active. Creating another event simply involves setting a new time window.