How octagonemusic/i3-dots works
Main components
• Repository Root ("i3-dots"): Acts as the central hub containing all submodules.
• Individual Application Configuration Folders:
• alacritty (terminal emulator config)
• dunst (notification daemon config)
• fastfetch (system information tool config)
• gtk-2.0 and gtk-3.0 (GTK settings for themes and UI)
• i3 (window manager config)
• picom (compositor config)
• polybar (status bar config)
• rofi (launcher/menu config)
• GNU Stow: Represent the tool used to manage symlinks from the repository to the user’s home directory.
• At the center, show the local repository ("i3-dots") which houses all dotfiles organized by application.
Architectural Patterns and Design Principles
• Modularity: Each application’s configuration is in its separate directory. This modular design allows selective symlinking using stow.
• Separation of concerns: Although all configurations are managed in one repository, each type of application is separated by its folder (for example, i3 configurations are entirely within the “i3” directory, polybar in “polybar”, and so on).
• Simplicity & Reusability: The use of a tool like stow emphasizes the reuse of configuration files while keeping the home directory uncluttered.
• Clear labels for each component (each configuration folder as a separate entity).
• Configuration repositories (group these together).
• Target system (the home directory) where symlinks are applied.
• Optional: Indicate minor components or extra configuration detail files (like the backup files or additional configuration snippets) if it helps in understanding the modular setup.