The time has come to unveil Grimoire, a bookmark manager designed specifically for everyone who is missing a little bit of magic touch when it comes to organizing their bookmarks.
Its mission is simple: to help you add, process, and organize your bookmarks in a way that makes sense.
Reasoning behind the project
I’ve always struggled with organizing my bookmarks. Even though I tried many options, none of them really appealed to me. The built-in bookmark managers in browsers were too basic and didn’t allow me to organize my bookmarks in a way that made sense to me. The most popular external bookmark managers have been too simple, too complicated, or too expensive for what they offer.
What I liked the most was the idea of having a bookmark manager with a relational database I had access to. This would let me retrieve my bookmarks in any way I wanted, and I could easily add new features in the future. I’ve searched for a solution that would allow me to do that, but I couldn’t find anything that would fit my needs.
And that’s how the idea of the Grimoire was born. I wanted to create a bookmark manager that would be simple to use, but also powerful enough to let me organize my bookmarks in a way that made sense to me. Moreover, I wanted to take SvelteKit and PocketBase for a spin, and this seemed like a perfect opportunity to do so.
How it looks now
Starting with v0.1.0, Grimoire has most of the basic features you would expect from a bookmark manager:
- bookmarks:
- can be added, viewed, edited, and deleted
- can be organized into categories and tagged
- metadata, like title, description, HTML content, favicon, and image, is fetched from the website and stored locally
- can have notes added to them
- bookmark list:
- display in a grid or list view
- can be searched by title, description, URL, and tags
- filtering by category, tag, and and more
- sort by date added, domain, and more
- users:
- can sign up and sign in
- all bookmarks, categories, and tags are private to the user
- admin panel:
- is used to manage users and see their bookmark, category, and tag counts
- can be used to preview most of PocketBase settings
- other:
- it’s dockerized, so it’s easy to run it locally or deploy it to your server
- all the benefits of a self-hosted PocketBase installation, like scheduled backups (local and to S3), high performance, and data security
- dark mode, because dark wizardry requires darkness
- responsive design as magic should be accessible to everyone, everywhere
- early and experimental support for AI-powered features (more on that in the future), like automatic tag suggestions
- and that’s just the beginning!
What’s next
It’s still a work in progress, but I’m happy with the functionality provided so far. You can expect more useful features, like a way to import bookmarks from other services and export them to most popular file formats, public profiles, better admin panel, AI-powered features - just to name a few. For more details, check out the roadmap.
How to get it up and running
If you want to try it out, you can run it locally!
Contributors are more than welcome
To make Grimoire even better, I need your help! Don’t be a stranger and check out the contributing guidelines today!
You must log in or register to comment.
Any advantages to this over Wallabag?
I don’t mean that in a confrontational way, this looks great! But I’d rather force myself to find a good reason before I replace Wallabag with it so soon after spending the effort getting it set up :P
It has not been possible to install it on a raspi4 (2GB) it stays installing forever… To be more specific, at this point:
=> [grimoire build 1/2] RUN --mount=type=cache,id=pnpm,target=/pnpm/store pnpm install --frozen-lockfile 429.3sI know that making your own image can be a real challenge when the output has almost 1GB. In next 24h I will try to put some images on Docker Hub.
I have quesion for you. Why do you use:
git clone git@github.com:goniszewski/grimoire.gitinstead of:
git clone https://github.com/goniszewski/grimoire.gitIt has many advantages over the HTTPS one. And also was always the preferred way of interacting with remote repositories by teams I worked with in my professional career.
I think this comment sums it up nicely: https://www.reddit.com/r/webdev/s/Ecg3lm5sfV
Looks cool!
Looks great, does it really “require” docker? Will it be difficult to run it from an lxc container?
A great question! Frankly, it can be launched via any JS package manager + PocketBase executable, so it shouldn’t be that hard.
That being said, at the beginning I would like to keep it simple and stick with Docker.