HN Showcase
Back to browse
Turning web highlights into deterministic Markdown (Sigilla)

Turning web highlights into deterministic Markdown (Sigilla)

by northerndev·Feb 16, 2026·1 point·0 comments
Visit ProjectView on HN

AI Analysis

●●SolidNiche GemSolve My ProblemSlick
The Take

Deterministic exports for Obsidian/Logseq are the selling point: highlights are tied to source and the app promises predictable Markdown/JSON output so your notes don't become a messy graveyard. The interface shows sensible features — reader view, tag/collection organization, AI search and spaced repetition — but this lives in a crowded space (Readwise/Hypothesis/etc.) so the export schema flexibility and third-party integrations will decide whether it becomes indispensable.

Category
Productivity
Target Audience

Researchers, knowledge workers, and PKM users who use Obsidian/Logseq and want predictable exportable highlights/notes

Post Description

I got tired of “read later” lists turning into a graveyard, and especially how messy exports are when you want to move notes into Obsidian/Logseq.

So I built Sigilla as a buffer layer: save an article, read it in a clean view, highlight + add notes, then export only the useful parts in a predictable format.

Example export looks like this:

"Article Title"

Saved: 2026-02-16 Tags: research, infra

Highlights

“Quoted highlight…” “Another highlight…”

Notes

My note linked to highlight 1

Another note

https://www.sigilla.net/

I’d love feedback on the export format/schema design. If you were piping this into your notes, what metadata would you want included by default (frontmatter, author, published date, content hash, etc.)?

Similar Projects