Come Through
approvedby mntno
Drill flashcards using spaced repetition.
Come Through
An Obsidian plugin for creating and reviewing flashcards by means of the FSRS algorithm.
Creating Cards
Each note can contain one or more cards. The contents of a side of a certain card is confined within the heading section that has declared the side. Card sides are declared using a Markdown code block with ct or comethrough as the “language”.
A front is declared like this:
```ct
side: front
```
Which will render:
ID: 1745575690288 Side: Front
The ID is automatically generated and is used to pair the front of a specific card with its back side. For example, to pair a back side to the front above, add the following to another heading section (that isn’t under the previous heading):
```ct
id: 1745575690288
side: back
```
[!NOTE]
The
idshould not be changed (once you rate the card for the first time) or it will be treated as a new card.
The id of this type of card (the default type) must be unique across the vault, which allows for declaring one side of a certain card in one note each. The following note, for example, contains three sides: one complete card and one front side.
# Note 1
Text here is not part of a card.
## Question Card 1
```ct
side: front
id: card1
```
Contents of the front of `card1`.
## Section without a card
Text here is not part of a card.
## Answer Card 1
```ct
side: back
id: card1
```
Contents of the back of `card1`.
### This section is included
Since this section belongs to the same section that declares the back of `card`, it is also included as part of the back of `card1`.
## Question Card 2
```ct
side: front
id: card2
```
Contents of the front of `card2`.
The back side to card 2 is declared in another file:
# Note 2
## Section
### Answer Card 2
```ct
side: back
id: card2
```
[!NOTE]
The card declaration format is plain YAML (same as Obsidian properties) so the YAML specification has to be adhered to. For example, there must be a space between the colon and the value.
Decks
To create decks, select Decks in the Command palette.
Reviewing
To review the cards, click / tap on Review in the ribbon or the Command palette.
Syncing
Syncing your vault across multiple devices can sometimes lead to conflicts, which may cause review statistics to be overwritten with older data. This can happen if you, e.g., rate on two or more devices while they are offline or before they have had a chance to sync. When the devices come online, the sync service may not be able to determine which version of the data is the correct one and will have to choose one version. To avoid this, the safest approach is to only make changes or rate on one device at a time.
However, as soon as changes are detected, a dialog is shown where you may accept or reject the change. Note that if you reject on one device, the next sync will cause the dialog to show on the other device(s), where you should then accept the change.
Roadmap
- More and quicker ways to create content to review.
- More ways to group defined content and select for review.
- Scheduler settings.
More
See the release notes for more details.
For plugin developers
Search results and similarity scores are powered by semantic analysis of your plugin's README. If your plugin isn't appearing for searches you'd expect, try updating your README to clearly describe your plugin's purpose, features, and use cases.