Use Cases

Research project

You're diving into a new topic — say, reactive programming on the JVM — and you want to keep all your references in one place.

1. Create a folder called Reactive JVM and assign it to your work circle.
2. As you find articles, documentation pages, and video tutorials, save each one as a bookmark inside that folder.
3. Add tags to each bookmark to distinguish content types: tutorial, docs, video, blog.
4. Write a short description on each bookmark to note the key takeaway — future you will be grateful.
5. Star the two or three most authoritative references as Favorites so you can reach them without hunting through the folder.
6. When the research is done, the folder becomes a permanent reference library. When you need to revisit the topic months later, everything is still there with your annotations intact.

Reading list

You constantly come across articles you want to read but don't have time for right now.

1. Create a folder called To Read (or use a tag-based approach — whatever suits you).
2. Whenever you find an article, save it as a bookmark with the tag to-read.
3. Add a one-line description of the topic so you can quickly triage what to read next.
4. Set aside time each week to open the folder, read an article, then edit its tags — remove to-read and add read — so your queue stays clean.
5. If an article turns out to be a keeper, tick Favorite after you read it.

Because All Bookmarks can be sorted by Newest, you can always find the most recently added unread items at the top without any extra filtering.

Team resource library

Your team needs a shared collection of links — internal wikis, tool documentation, onboarding guides — that everyone in the circle can access.

1. Create a folder structure that mirrors your team's areas: Frontend, Backend, DevOps, Onboarding.
2. Assign all folders to the shared team circle so every team member can see them.
3. Add bookmarks for internal tools (CI dashboards, runbooks, design system), external documentation, and important decision records.
4. Use tags like onboarding, runbook, reference, tool so new team members can filter by type across all folders.
5. When a tool changes or a URL moves, any team member with write access can update the bookmark in seconds — no more stale links in Slack messages.

Personal knowledge base

You're a developer (or designer, writer, etc.) who accumulates a large number of reference links over time and wants to be able to find anything within seconds.

1. Create a root folder for each major domain of your work: Frontend, Backend, Design, Productivity, Career.
2. Add subfolders where the topic is large enough — e.g. Frontend → CSS, Frontend → JavaScript, Frontend → Tooling.
3. Tag every bookmark with at least one content-type tag: docs, tutorial, tool, article, cheatsheet.
4. Use the All Bookmarks search to find anything by title, URL, or description keyword — no need to remember which folder you filed something in.
5. Sort by Most Visited periodically to discover which references you rely on most; star those as Favorites.

Bulk import from another tool

You're migrating away from another bookmark manager (or have a curated list in a spreadsheet) and want to bring everything in without doing it manually one by one.

1. Export or convert your existing data into the Bookmarks JSON format. Each logical group of links becomes one file with its own folderName.
2. Use the Import feature (sidebar → Import) to upload each file, selecting the appropriate circle each time.
3. After each import a new folder is created automatically. Review the contents and edit individual bookmarks to add missing descriptions or tags.
4. Repeat for each batch until your full library is migrated.

The import validates the entire file before writing anything, so a formatting mistake in one entry won't leave you with a half-imported folder. Fix the errors shown, re-upload, and the whole batch goes in cleanly.

Shopping and wish lists

You want to track products you're considering buying — spread across multiple sites — without browser tabs piling up.

1. Create a folder called Wish List (or one per category: Tech Gear, Books, Home).
2. Save each product page as a bookmark with a description noting the price, key specs, or what you like about it.
3. Tag items with compare while you're still deciding, and change the tag to decided once you've made up your mind.
4. When you've bought something, delete the bookmark to keep the folder clean. If you might want to reorder, star it as a Favorite instead.

Onboarding a new team member

You want to give a new colleague everything they need on day one without a lengthy walkthrough.

1. Create a folder called Onboarding — [Name] in the team circle.
2. Add bookmarks for: the company wiki, internal tool URLs, the team's coding standards page, CI/CD documentation, and any project-specific READMEs.
3. Use descriptions to add context: "Our staging environment — use these credentials from 1Password", "The design system — check here before building any new UI component".
4. Star the three or four most critical links as Favorites within the folder so they surface first.
5. Hand off the folder link on day one. The new team member has a structured, annotated reference they can revisit at their own pace — and that you can keep updated as tools change.