How danielrouco/dotfiles works
Project Context and Purpose
• This is a dotfiles repository meant for personal use. It configures the Linux desktop by providing preconfigured settings for various applications.
• The tools include Sway (window manager), Waybar (status bar), Wofi (application launcher), Foot (terminal emulator), Dunst (notification manager), Neovim (text editor), Zathura (PDF viewer), and Ranger (file manager).
Main Components
• Sway: The core tiling window manager, which acts as the central component managing windows and input.
• Waybar: The status bar for displaying system and workspace information, directly interfacing with Sway.
• Wofi: The application launcher that integrates with the desktop environment.
• Foot: The terminal emulator, a fundamental tool for command-line operations.
• Dunst: The notification manager, which handles system alerts.
• Neovim: The text editor, essential for code and text editing.
• Zathura: The PDF viewer with vim-style keybindings.
• Ranger: The terminal file manager, also employing vim keybindings.
• .bashrc and other user-specific configurations: Provide shell environment setup and additional customizations.
Establish Relationships and Interactions
• Waybar should be connected directly to Sway, showing that it relies on the window manager to determine what to display (like workspace and window information).
• Directional flows, for example:
• User inputs or starts session → Sway initiates the desktop environment.
• Sway → Launches Waybar (for status information), Wofi (for application launching), and integrates notifications (Dunst).
• Foot, Neovim, Zathura, and Ranger operate within the Sway environment as applications triggered by user interactions.
Architectural Patterns and Design Principles
• Although these configuration files don’t form a “runtime” architecture in the traditional sense, they illustrate a modular design where each tool is independently configured while smoothly integrating into the overall system.
• Follow separation of concerns: each tool’s config file (e.g., sway/config, waybar/config.jsonc, foot/foot.ini) is encapsulated in its own directory.
• Dependency relationships: user environment settings (.bashrc and user-dirs) feeding into system-level configuration.
Incorporate Relevant Technologies and Configuration Files
• Out each tool along with their primary configuration file:
• Sway → sway/config
• Waybar → waybar/config.jsonc, waybar/style.css
• Wofi → wofi/style.css
• Foot → foot/foot.ini
• Dunst → dunst/dunstrc
• Neovim → nvim/init.lua (and lazy-lock.json indicating plugin or lazy runtime management)
• Ranger → ranger/rc.conf, ranger/rifle.conf
• Zathura → zathura/zathurarc
• Shell environment → .bashrc
• Optionally mention user directories config files (user-dirs.conf, user-dirs.dirs) used to structure user file locations.