20
Boxing: an open-source new tab where bookmarks live in boxes on an infinite canvas (Apache-2.0) (github.com)
submitted 3 weeks ago by to c/opensource@lemmy.ml
12 comments fedilink hide all child comments
 

I'm the author. Boxing turns the new tab into a canvas: big boxes hold small boxes, small boxes hold bookmarks, and you can drag, connect and zoom.

The part that might interest people here: every design call is written up as an ADR in the repo, including the ones I reversed. A free hue slider got replaced by 5 hand-tuned themes because it allowed ugly combos (ADR-0012). The font sizes all derive from one base value with an 11px floor (ADR-0019). WebDAV sync went from last-write-wins to a per-box three-way merge with a snapshot before anything gets overwritten (ADR-0009). There's also a contrast check in CI that fails the build if a clickable control relies on a too-faint border.

No analytics, no tracking. Data lives in browser storage; WebDAV or Gist backup is opt-in. Plain JS, Manifest V3, 14 languages, on the Firefox and Edge add-on stores.

https://github.com/Xxx91n/boxing

Happy to hear where the design or the code is wrong. Translation fixes are very welcome too.

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 3 weeks ago (3 children)

I feel like this is over engineering. We are talking about bookmarks here. I don't get what the reason is to have this. Bookmarks can already be organized in folders and have tags and description.

  • permalink
  • fedilink
  • source
  • hideshow 3 child comments
    •
  • [–] [S] 4 points 3 weeks ago (2 children)

    Fair question. It started with Obsidian's canvas. I used it for bookmarks for a while and liked how it felt like tying a bunch of links together with string, kind of branching out like neurons. But I didn't want to open Obsidian every time, so I just built a canvas with drag and drop and connecting lines into the new tab page instead.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 3 weeks ago (1 child)

    I see. Well that makes sense at least. I would recommend to leave that information in the README too, as it brings it into perspective.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] [S] 5 points 3 weeks ago

    Yeah, you're right, it should be in there. Honestly this makes me want to rework the README in general. Right now it reads a bit like a showcase, and it doesn't really say why the thing exists. I'll put the canvas / tied-together-links idea up front so people can tell quickly whether it's for them or not.

    Also, I'm enjoying the vibe here. People just say what they think, which is what I wanted.

  • permalink
  • fedilink
  • source
  • parent