Bookmark management for academics

Academic workflows pile up artefacts that don't fit a reference manager: syllabi, reading lists, conference talk pages, grey literature, course materials, public lectures. A bookmark archive that plays well with Zotero or Mendeley covers the gap.

Where bookmarks complement reference managers

• Syllabi and reading lists. Course pages, bibliography PDFs, recommended-reading posts. Save once, tag by course code, reuse for the next cohort.
• Talks and lectures. YouTube recordings, conference session pages, slide decks. Citable in some style guides; harder to handle as references in others. Bookmark archive smooths that.
• Grey literature. Working papers, white papers, governmental reports. Often unstable URLs; bookmark + archive.org backup is more robust than waiting for Zotero to import a flaky page.
• Teaching resources. Datasets, demo apps, notebooks, problem sets. Categorised by course, by topic, by intended audience.

A workflow that survives a semester

1. One collection per course. Everything a course consumes — readings, lecture links, demo videos, supplementary material — sits in its own collection. The collection becomes the course's permanent archive.
2. Topics cross collections. A topic like diffusion models can appear across the undergraduate ML course, the graduate generative-models seminar, and your own research collection. The graph composes; the courses don't.
3. Periodic export for course handover. When you pass a course to a colleague, export the collection to Markdown or HTML. They get a complete, structured record of the previous syllabus's web material.
4. Share a topic, not a folder. A reading list on fairness in ML is a topic export — filtered list of every link tagged that topic, with descriptions, in a clean document. No screen-share required.

Privacy considerations

Academic accounts often get co-opted into institutional analytics. Saving research interests through a service that monetises them is worse than careless — it's a slow leak of your research agenda.

A bookmark archive stored in your own Solid pod never crosses a vendor's analytics boundary. The app reads and writes; nobody profiles the contents.

Compatibility with Zotero, Mendeley, JabRef

Reference managers and bookmark archives serve different needs. Citable items go in Zotero with full metadata; everything else goes in the bookmark archive. The two cross-link via shared IDs in descriptions — when a bookmark eventually does earn a Zotero entry, paste the citation key into the bookmark description. Bookmark search then surfaces it alongside the rest of the topic.