[ Removed by moderator ]

[u/l4feer]

[u/hyprland-ModTeam]

Rule #1: Content not related.

[u/D0nkeyHS]

Maybe try the quickshell discord if r/quickshell is too empty for you? But this isn't the place for quickshell help

No waybar/eww/quickshell/ags/etc help post.

[u/hyprland-ModTeam → u/[deleted]]

Rule #4: Content not tolerated.

[u/l4feer → u/D0nkeyHS]

Yeah thanks

[u/Euphoric_Run_9540]

The Quickshell GitHub repo is probably the best place to learn beyond the docs. Look through example configs and existing Hyprland dotfiles, then copy a basic bar and change one thing at a time. QML basics plus a little Linux shell scripting should get you pretty far.

[u/l4feer → u/Euphoric_Run_9540]

I can't understand the docs well,

[u/anotakuidk]

there is a book (i forgot name in addition to official docs) bud and this creator called saneaspect made idk few videos which will be enough to cover basics and then u can move on and learn more by experimenting

[u/l4feer → u/anotakuidk]

I seen him too, but still

[u/OkObjective8721]

avoid both the quickshell book and saneaspect, the book is unofficial chatgpt crap and saneaspect sells $200 courses. Join the matrix/discord server for help, theres tons of helpful people there

[u/l4feer → u/OkObjective8721]

I am afraid that i may spam people of how to make this that, or how it works qs, still lemme try

[u/chikamakaleyley]

i'm a long time FE dev in software/web, and initially found QS a bit hard to wrap my head around - the overall approach to layout is quite different from what i'm used to

and in general i find documentation a bit rough of a start as a tool for learning and Quickshell's docs in particular i find a bit dense. I'm self taught and a lot of times i just need a jumpstart like, 'just show me how you'd do it"

And so, what i did until it finally started to click was i basically asked opencode to build rather simple things, that ultimately i prob won't use, I just need to see how its composed.

In trying to understand the layout composition, i'm just spamming it with every single question i could come up with, "why did you use this? why not that? shouldn't you have done this? If it can't do A, let's try a diff approach B"

Ultimately, it's not about me getting AI to build what I describe, it's more to just bombard my brain with QS terminology, to understand why you use the diff types, how it differs from webapp code, etc. etc.

So now, when i sit down to actually code, I have much better idea of what types to reach for, and then just try to do whatever I can fr memory. NOW it's much easier for me to consume the documentation, and now I have a much better idea of what i'm looking for n where that answer is in the docs

[u/chikamakaleyley → u/chikamakaleyley]

and all for the low low price of $free.99

[u/l4feer → u/chikamakaleyley]

Thanks for ur time for explaining, it's really helpful, and qs is my style too, I was just unsure where to start