OUoutofpaper·Dec 14, 2025
Another plain text option is
David Miserak's GoCard.
https://github.com/DavidMiserak/GoCard
In Hashcards: A plain-text spaced repetition systemDavidMiserak
GoCard
Go2025–2025
DavidMiserak / GoCard
GoCard
A lightweight file-based spaced repetition system (SRS) that uses plain Markdown files for flashcards. Perfect for developers who prefer text files, Git version control, and keyboard-driven interfaces.
2Distinct people
2Mentions
0Explicit recommenders
60GitHub stars
What to know before exploring
What it is
A lightweight file-based spaced repetition system (SRS) that uses plain Markdown files for flashcards. Perfect for developers who prefer text files, Git version control, and keyboard-driven interfaces.
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by month2 dated mentions
Observed mentions: 2025-03-22 21:05:07 UTC to 2025-12-14 22:28:42 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Mar 2025 | 2025-03-01 00:00:00 UTC | 2025-04-01 00:00:00 UTC | 1 | 1 | 0 |
| Apr 2025 | 2025-04-01 00:00:00 UTC | 2025-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2025 | 2025-05-01 00:00:00 UTC | 2025-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2025 | 2025-06-01 00:00:00 UTC | 2025-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2025 | 2025-07-01 00:00:00 UTC | 2025-08-01 00:00:00 UTC | 0 | 0 | 0 |
| Aug 2025 | 2025-08-01 00:00:00 UTC | 2025-09-01 00:00:00 UTC | 0 | 0 | 0 |
| Sep 2025 | 2025-09-01 00:00:00 UTC | 2025-10-01 00:00:00 UTC | 0 | 0 | 0 |
| Oct 2025 | 2025-10-01 00:00:00 UTC | 2025-11-01 00:00:00 UTC | 0 | 0 | 0 |
| Nov 2025 | 2025-11-01 00:00:00 UTC | 2025-12-01 00:00:00 UTC | 0 | 0 | 0 |
| Dec 2025 | 2025-12-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
2 sourcesShow HN: GoCard – A file-based spaced repetition system built in Go
Hi HN! I'm excited to share GoCard, a terminal-based spaced repetition system I built that uses plain Markdown files as its data source.
I've always been frustrated with existing spaced repetition tools that lock my knowledge into proprietary formats or require constant internet access. As a developer who lives in terminals and text editors, I wanted something that:
1. Stores cards as plain text files I can edit with any editor
2. Works seamlessly with Git for versioning and sync
3. Runs in a terminal without distractions
4. Has first-class support for code snippets and programming concepts
GoCard implements the SM-2 algorithm (the same one used by Anki) but instead of a database, it uses a simple directory structure where:
- Each card is a Markdown file with YAML frontmatter
- Directories represent decks and subdecks
- Everything is edit
Read the rest
able with standard tools
*Key features:*
- Distraction-free terminal UI built with BubbleTea
- Real-time file watching (edit cards in your editor while reviewing)
- Code syntax highlighting for 50+ languages
- Vim/Emacs keybindings for efficient navigation
- Hierarchical deck organization via directories
- Cross-platform (Linux, macOS, Windows)
What sets GoCard apart from other SRS tools is its developer-centric approach. Create cards with your favorite editor, organize them with your file manager, version them with Git, and review them in a clean terminal interface.
I built this because I wanted a knowledge management system that worked with my developer workflow rather than against it. Making everything file-based means I can apply all my existing text-processing skills and tools.
The project is v0.1.0, implemented in Go, and available at: https://github.com/DavidMiserak/GoCard
I'd especially appreciate feedback on the UX design and any suggestions for making it more intuitive for terminal users. Has anyone else built similar file-based knowledge tools? What patterns worked well for you?