File
SMF·NUCLINO
Received on
31.07.2026
Reviewed on
28.09.2026
Exhibits annexed
3
Questions
4

SMF·NUCLINO

Can a prompt replace Nuclino?

Notes & knowledge management — notes, wikis and personal knowledge bases

Almost Verdict recorded on 28.09.2026 · Verified on 31.07.2026
Price
$8/moSource: nuclino.com · Checked on July 31, 2026
Per year
$96
Build time
One sitting
Votes
0 votes
YesAlmost (checked)Not yet

Exhibit tracking slip

Exhibit A The prompt
Exhibit B What you lose
Exhibit C Why people still pay: sync, collaboration, and capture polish
Exhibit Q Questions

Verdict

A minimal team wiki with a visual board view — arrange pages spatially on a canvas instead of just a linear list — is a real weekend build. What doesn't survive: real-time multiplayer editing, a hard problem this catalogue has flagged repeatedly, and years of polish in how the visual board handles hundreds of pages without becoming cluttered.

Exhibit B — What you lose

Exhibit A — The prompt

Received on31.07.2026
Build a minimal team wiki with a visual board view as an alternative way to browse pages, on top of a fixed data model rather than Nuclino's own real-time collaborative engine. Use Next.js/TypeScript with Postgres. Support Markdown pages organized into named collections, a lightweight wiki structure with no deep nesting. Build two views per collection: a standard list view, and a board view where each page is a draggable card positioned freely on a 2D canvas, with position saved per page. Support [[wiki-links]] between pages with backlinks shown at the bottom of each page. Implement basic version history: save a snapshot on each edit, viewable as a list of past versions with a simple text diff, not a fancy visual diff, between any two. Add full-text search across all pages in the workspace. Do not build real-time multiplayer editing, the same honest limitation as this catalogue's other team-tool entries, since conflict-free concurrent editing is genuinely hard; use last-save-wins with a warning if the page changed since you started editing. Requires hosting and a database; no external API key needed.

Opening prefills the prompt — press enter to run it.

Exhibit B — What you lose

  • B.1 real-time multiplayer editing
  • B.2 polish in how the board view scales to hundreds of pages
  • B.3 version history with visual diffs
  • B.4 cross-workspace search

Prior art

Exhibit C — Why people still pay: sync, collaboration, and capture polish

A board view with draggable cards is a real but bounded UI project; real-time collaborative editing without conflicts, which a team wiki genuinely needs, is the hard problem this catalogue keeps naming rather than solving casually.

Questions

Can multiple people edit the same page at once?

Not safely — like several other team tools in this catalogue, real-time conflict-free collaborative editing is flagged as genuinely hard rather than attempted casually. This build warns you if the page changed since you started editing, rather than silently overwriting.

What's the board view actually for?

Arranging pages spatially, by topic or relationship, as an alternative to browsing a flat list — useful for seeing how a project's pages relate to each other visually.

Does it have visual diffs between versions?

A simple text diff, not Nuclino's more visual comparison — enough to see what changed, though less polished.

What does it cost to run?

Hosting and a database — typically a few dollars a month for a small team, with no per-seat fee.

Receipt

Already built this yourself?