How narmis-e/onedark-wallpapers works
What this project is (type + purpose)
This repo is not an application/service—it’s a curated asset collection (wallpapers) organized into themed directories, with a README describing the visual design goal: wallpapers colorized to match the OneDark palette (referencing onedark.vim, Atom One Dark greys, and workflows like ImageGoNord; future: tint).
What the file tree implies about structure
Top-level directories are essentially categories/collections:
• minimal/ (and minimal/torvalds/): minimal-style wallpapers and a sub-collection
• os/: OS-themed wallpapers
• wm/: window-manager-themed wallpapers
• programs/: app/program-themed wallpapers
• botw/: likely a themed set (e.g., Breath of the Wild)
• misc/: catch-all / uncategorized
• showcase.md: gallery/preview document (noted as “Todo: fix showcase gallery”)
• LICENSE, README.md: repo metadata/documentation
There’s no src/, no build scripts, no CI config visible, no code. The “architecture” is primarily:
What the README adds (key architectural facts)
• Palette specification:
• OneDark palette from joshdick/onedark.vim
• Additional greys from Atom One Dark 2
• Processing tools:
• Current: ImageGoNord (IGN)
• Future replacement: tint (explicit TODO)
• Manual touch-up sometimes implied (e.g., “touch it up by making the bg blue again” and GIMP hex mismatch TODO)
• Sources:
• Reddit, unixporn Discord, Wayback archives of other collections, Nordic repo, Imgur dumps
• Constraints:
• Images are ≥ 1920×1080, some up to 5K
• Community workflow:
• Contributions & requests via issues/PRs
• Removal requests process
External Sources
• Reddit / Discord / Wayback archives / other wallpaper repos / Imgur dumps
Acquisition / Curation
• Human curator (repo maintainer)
• Optional: “selection criteria” (resolution threshold, theme fit)
Processing Pipeline
• Automated colorization tool: ImageGoNord (current)
• Planned tool: tint (future)
• Manual editing tool: GIMP (implied by TODO)
• Output: OneDark-colorized images (final assets)
Repository Organization (Artifact Store)
• Folder taxonomy: minimal/, os/, wm/, programs/, botw/, misc/
• Special subcollection: minimal/torvalds/
Contribution & Governance
• GitHub Issues (requests, removal requests)
• Pull Requests (contributions)
• Licensing (LICENSE)
• External Sources → Acquisition/Selection
• Acquisition/Selection → Processing Pipeline
• Processing Pipeline → Manual Touch-up (optional branch)
• Processing Pipeline / Manual Touch-up → Repository Organization (commit assets)
• Repository Organization → Documentation/Showcase (gallery consumes folder assets)
• Contributors → PRs → Repository Organization
• Users/Creators → Removal Requests (Issues) → Maintainer → Repository changes
Architectural patterns/design principles present
Even without code, there are clear patterns:
• Asset pipeline pattern: ingest → transform → publish
• Taxonomy-first organization: folders represent “domains” (minimal/os/wm/programs/etc.)
• Human-in-the-loop processing: automated filter + manual corrections
• Community-driven inputs: issues/PRs govern changes
Relevant technologies/tools prominently
These matter more than “frameworks” here:
• ImageGoNord (current transformation)
• tint (planned replacement)
• GIMP (manual adjustment)
• GitHub (repo hosting + issues/PR workflow)
• OneDark palette sources (onedark.vim; Atom greys)
External Sources (clouds)
• Reddit, Discord, Wayback archives, Nordic repo, Imgur dumps
Curation (process)
• select, verify resolution, pick theme/category
Colorization (process)
• ImageGoNord (current)
• (future) tint
Manual QA/Touch-up (optional process)
• GIMP adjustments (noted hex mismatch issue)
Publish (artifact store)
• commit into minimal/, os/, wm/, programs/, botw/, misc/
Community Loop (governance)
• contributors via PRs
• requests/removals via Issues
• root
• botw/
• minimal/
• torvalds/
• misc/
• os/
• programs/
• wm/
• README.md
• .md
• LICENSE
Folder node with the “theme intent” (minimal, OS-specific, WM-themed, etc.).
“Separate into as many components as possible” (without overthinking)
For maximum detail (useful at principal level), explicitly split:
• “Palette spec” vs “Tool implementing palette mapping”
• “Automated transform” vs “Manual correction”
• “Storage taxonomy” vs “Gallery rendering” (even if it’s just markdown)
• “Contribution workflow” vs “Removal workflow”