How e33io/scripts works
Main Components Organization
• Installation Scripts (Core)
• Desktop Environment Scripts
• Application Installation Scripts
• Theming Scripts
• Utility Scripts
Component Relationships
a) Primary Flow:
• Branching paths to different DE/WM installation scripts
b) Secondary Systems:
• Related scripts (e.g., theming scripts, utility scripts)
• Which scripts are distribution-specific (Debian vs openSUSE)
Specific Elements
Create sections for:
a) Distribution-Specific Scripts:
• Debian-based scripts
• openSUSE scripts
• Ubuntu-specific scripts
b) Functionality Groups:
• Window Manager installations (i3, JWM)
• Desktop Environment installations (XFCE, LXQt, MATE, Cinnamon, GNOME)
• Browser installations (Brave, Firefox, LibreWolf)
• System utilities (swap, tearfree, wakelock)
Important Relationships to Highlight
• Dependencies between scripts (e.g., theming scripts depending on DE installation)
• Optional components vs. required components
• System modification flows (e.g., display, theme changes)
Additional Details
• Notes about script execution requirements (root privileges, prerequisites)
• Version compatibility information
• Scripts that require user interaction
• Entry points at the top
• Core installation scripts in the center
• Utility and optional scripts branching to the sides
• Clear pathways showing different installation combinations
Remember to:
• Keep the abstraction level appropriate (focus on script relationships rather than internal script details)
• Use consistent styling throughout
• Clear labels for all components
• Brief descriptions for key components
• Both mandatory and optional paths clearly
• The overall structure of the script collection
• How different scripts interact and depend on each other
• The various installation paths available
• System modification possibilities
• Distribution-specific considerations