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.

  • londos@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    4 hours ago

    This is very AI, but it also seems like one of those things that OP has probably been dwelling on in their head and made it just for themselves. This will be unpopular, but its not the worst thing.

    I’d advise OP to be content being the only one to use it. Make it for yourself exactly as you would use it. Don’t bother with design decision documentation no one will ever read or user config options that are irrelevant to anyone but you. Get the concept working as you imagine, stop, and see if you can try doing the next commit without the LLM.

  • thingsiplay@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    7 hours ago

    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.

  • ghost_laptop@lemmy.ml
    link
    fedilink
    arrow-up
    2
    ·
    14 hours ago

    i have like 5000 bookmarks, how am i supposed to visualize them with this? i’m thinking my pc will blow up having to render that many stuff, specially since it’s JS.

    • xxx91n@lemmy.worldOP
      link
      fedilink
      arrow-up
      2
      ·
      15 hours ago

      ADR = Architecture Decision Record. Not tickets, more like short notes, one per decision: what the problem was, what I picked, what I gave up. e.g. why there’s no free hue slider anymore, or why boxes have zero shadow until you hover. Mostly so future me doesn’t undo something I already argued with myself about. They’re in docs/adr if you’re curious.

      • Dave.@aussie.zone
        link
        fedilink
        arrow-up
        2
        ·
        7 hours ago

        Mostly so future me doesn’t undo something I already argued with myself about. They’re in docs/adr if you’re curious.

        Mostly so future LLMs don’t undo something they already argued with themselves about.

    • davidgro@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      18 hours ago

      Apparently “architecture decision records”, I found that in START-HERE.md - It looks to me like an internal ticket system.