How archcraft-os/archcraft-openbox works
Project Type and Purpose
• This is neither a web app nor a service-oriented system, but a Linux configuration/theme package for the Openbox window manager (an Archcraft Openbox “dotfiles” / theming repository).
• It provides:
• A PKGBUILD and install scripts to build/package the config.
• A “files/” directory containing per-application config snippets (Alacritty, Kitty, Rofi, Tint2, Polybar, Plank, pipemenus, Nitrogen, etc.).
• A “themes/” directory of dozens of complete theme sets, each with subfolders for polybar, rofi, tint2, wallpaper, and an apply.sh script.
File-Structure Analysis
• Top-level:
• build.sh / PKGBUILD / archcraft-openbox.install → build & package management
• files/ → application configurations and scripts
• themes/ → multiple theme bundles
• The patterns show a clear separation of concerns:
• Build & install layer → packaging logic
• Config layer → static config files and helper scripts
• Themes layer → theme directories, each with its own apply.sh
README Insights
• Single documentation link pointing to Archcraft Openbox wiki
• No embedded architecture doc, so we reverse-engineer from the file tree
Main Components & Relationships
a. Components
• Build/Package Component: build.sh, PKGBUILD, archcraft-openbox.install
• Configuration Component: files/ directory
• Theme Component: themes/ directory (sub-themes)
• Runtime Components: Openbox WM, Alacritty, Kitty, Rofi, Polybar, Tint2, Plank, pipemenus, Nitrogen, NetworkManager-DMenu scripts
b. Interactions
1. Developer runs build.sh → invokes PKGBUILD → produces an Arch package
2. Package installer (pacman) triggers archcraft-openbox.install → copies files/* to ~/.config and themes/* to ~/.config/archcraft-themes
3. At session start:
• Openbox reads its rc.xml, menu definitions, autostart
• Autostart scripts launch Polybar, Tint2, Plank, Nitrogen, keybindings, rofi menus, etc., each reading their configs from ~/.config
4. Theme switching:
• User runs themes/<theme-name>/apply.sh → executes a series of file copies or symlinks to update each component’s config → restarts/reloads affected components
c. Architectural Patterns
• Separation of build vs. config vs. theme data
• Declarative theme bundles with a uniform structure (apply.sh + subfolders)
• Convention-over-configuration: each app expects config in ~/.config/<app>
d. Key Technologies
• Shell scripts (bash) for build/install/apply
• pacman packaging (PKGBUILD)
• Openbox WM
• Applications: Alacritty, Kitty, Rofi, Polybar, Tint2, Plank, Nitrogen, NetworkManager-DMenu