Repository navigation
Replies: 1 comment 1 reply
|
Thanks for sharing srmd! Spaced repetition is out of scope for Foam itself. Foam’s core is about writing, linking and navigating notes. Flashcards bring their own syntax, scheduling data and review workflow, and those are better owned by a dedicated extension than built into Foam, exactly as you are doing. We’re not planning a move to micromark, we’re working on parser performance and the parser may change, so we don’t want other extensions depending on parser hooks yet. I don't think that would be a problem for you, a second pass over just your .sr.md files should be cheap anyway. For link resolution you can already use Foam’s extension API: The embed problem is a Foam bug. I am fixing that in #1762 . |
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I have a project, srmd, to extend note taking with Foam: flashcard/cloze deletion syntax for Markdown with the goal of making flashcards as unobtrusively as possible from kb-style notes using FSRS. The project has a VS Code extension, that aims to play nice with Foam, and an Android app for phone use at the moment.
The idea is to keep note-taking first and allow unobtrusive markup that can turn the note into flashcards rather than having to deliberately design flashcards. Therefore the format is not similar to Obsidians but rather something like the following in the simplest form:
Where the
::marks the cloze deletion start and Markdown structure determines the end. Several additional features are available allowing for cloze grouping, nesting and explicit start/end points. Additionally a tree view is added to vs code displaying note hierarchy and card due data as well as a separate review webview which renders the cards with a review UI handling scrolling to relevant section, showing/hiding of clozes, grading etc.At the moment the code base, originally hand rolled, contains a fair amount of AI slop to move the project from stalled to usable - I apologize for that and intend to review it in detail. At the moment the VS Code extension is a free-standing thing using micromark (and remark for Markdown formatting), nothing prevents it from being used together with Foam but it doesn't integrate Foam features like wikilinks, embeds etc. I would much rather fully integrate with Foam but there are a couple of obstacles as I understand the current Foam core right now:
Thoughts? What are your plans and would PR's be welcome and if so, how extensive? I understand it as that you are planning a move to micromark?
Thanks
All reactions