practicalli / practicalli/engineering-playbook

os: hyprland and related projects

Open
#29 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Makefile
Stars
12
Forks
5
PR merge metrics
No merged PRs in 30d

Description

What is hyprland (and what it isnt - ie a desktop environment)

Hyprland is suited to those who wish significant customisation and are prepared to put in the work. Hyprland itself is not a desktop environment, so very limited scope without other projects.

Install options

Desktop environments

  • nwg-shell - GTK3-based shell for sway and Hyprland Wayland compositors

NOTE: GTK4 is the current stable. Assumption: GTK3 will be available alongside GKT4 until GTK5 is released (probably 2-3 years)

Configurations (dotfiles)

Related projects / ecosystem

Documentation

Community

Copy ?

What is hyprland (and what it isnt - ie a desktop environment)

Hyprland is suited to those who wish significant customisation and are prepared to put in the work. Hyprland itself is not a desktop environment, so very limited scope without other projects.

Install options

Hyprland tools

  • hyprpaper wallpaper management
  • waybar

Desktop environments

  • nwg-shell - GTK3-based shell for sway and Hyprland Wayland compositors

NOTE: GTK4 is the current stable. Assumption: GTK3 will be available alongside GKT4 until GTK5 is released (probably 2-3 years)

Configurations (dotfiles)

Related projects

Documentation

Community

Set up Git

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No target file, test, or entry point is named. First locate where this guide belongs in the repository, then review the duplicated draft and its Hyprland installation, ecosystem, documentation, and community links. Done means one coherent guide with unfinished entries removed and the referenced links checked.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
documentation, operating-systems
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.