Every site worth keeping, in one list
"instead of forty open tabs"
The framework whose docs actually explained the build step, the styling site you copy grid values from every week, the database engine comparison you keep re-reading, the deployment tool that saved the release. A Glubler is a list of those websites, grouped by what you use them for, and it stays a list you can open rather than a stack of tabs you can never find again.
Collect the sites you use and group them by what they do
A developer already knows the answer to "what should I use for routing" — the problem is that the answer is scattered across a bookmark folder nobody has opened since 2023, a Slack DM, and a tab that died with the laptop. Glue the websites into a Glubler and the whole list opens in one place, sorted by whether you reached for them for the front end, the back end, the data layer or the deploy. Add a site when you find a good one, and the list gets more useful every time you use it.
api-gateway.dev
schema-hub.io
db-engines.net
queue-tools.org
auth-specs.com
Saved sites
A Glubler for each kind of work you do rather than one enormous list
Frontend libraries, backend and API resources, database and data tooling, the deployment and monitoring sites — none of them answer the same question, so there is no reason to keep them in one pile. A Glubler per area means the list you open is the list for the job in front of you, and a database professional reading the same page finds the engine comparisons rather than someone else’s CSS framework. Subglublers nest inside one another, so a team keeps everything under one profile and still hands each person the half that concerns them.
Dev Toolbox24 sites
API Stack11 sites
Frontend
Backend
Data
Ops
Shared lists
Hand the list to the team with the sites already in it
A starter project usually begins with someone pasting a folder of links into a document, and that document is stale within a month. Share the Glubler instead and a new developer opens the same curated list your team already trusts, adds the sites they find, and the whole group benefits. No onboarding doc to maintain, no links to rot in a README nobody updates.
Start a collectionKeep the whole site, not the snippet you copied
A fragment of documentation pasted into a notes file is worth nothing eighteen months later — it has no version, no link, and no indication of which library it came from. Collect the website itself and you keep the address, the current version and every page underneath it, so the list still works after the site is redesigned. One Glubler for the front end, one for the back end, and neither has to be re-typed when a tool you rely on changes.
Group the lists by the job, not the vendor
A database professional, a backend engineer and someone picking a frontend framework are all building collections, and none of them want the other two’s links. Sorting each list by purpose rather than by product keeps a single Glubler useful to every kind of developer on the team, and makes a list you can hand to a new starter instead of a page they have to filter. As the list grows it becomes the record of what your team actually reaches for — which is worth more than any single bookmark.
A collection that stays current
Sites get redesigned and moved, so a bookmark folder from two years ago quietly points at nothing. Collect the current version of a site into the Glubler that already holds it and the list updates as one entry, your note on what you use it for included. The list you reach for is the list that is still live.
One Glubler per kind of work
Frontend, backend, database, deployment — each list answers a different question, so keeping them apart means the list you open is the one for the job in front of you. Subglublers nest under a single profile, so a team can keep every list it maintains in one place while each person still sees only the ones they need.
Borrow the lists other developers already trust
Every Glubler is a public collection unless you close it. Follow the developers whose judgement you rate and their lists arrive in your feed — a frontend set for a project you are starting, a data-tooling group for a migration you thought was undocumented. You take their list and add the sites your own stack needs.
Glubler FOR
DEVELOPERS
Your lists, in public
Every Glubler is a website collection, not a private folder. Publish the sites you reach for, what you use each one for and why — then build on the lists of developers whose judgement you already rate.