Version 4.1.0 · All versions

All pages

Browsing and editing cards

The screens where a learner makes a deck, looks through its cards and changes them, and where they look through a library deck before they import it. A deck of one's own is edited in one place, the Browser; a library deck can only be looked at, until it is imported.

The Studio does the same work in bulk, for many decks and cards at once. This page is about Solid Memo's own screens. Their routes are in routing.md; writing a card in Markdown is in markdown.md.

The deck creator

#/new-deck, from "Create deck" under the deck list. It asks for one thing, the deck's name, and the language the name is in. The language starts as the one last chosen for a deck's text on this device, else none: the app does not guess it from the page, and creating a deck whose name has no language says so and puts the focus on the language picker. Once created, the deck is on the deck list (DeckCreatorScreen.tsx, DeckCreatorContainer.tsx).

The Browser

#/browse, from "Browser" on a deck's page. It is the one place a deck and its cards are edited (BrowserScreen.tsx, BrowserContainer.tsx). From the top:

The page and the filter are in the URL. Paging and changing the filter replace the history entry, so Back leaves the Browser instead of walking every page; opening a card pushes one, so Back from a card returns to the same page and filter. A page past the last shows the last (Pager.tsx).

The card creator

#/new-card, from Add card in the Browser (CardCreatorScreen.tsx, CardCreatorContainer.tsx, AddCardForm.tsx). Each side of a card needs text, a picture (a web address), or both. Optional fields add a description of each picture, read out to anyone who cannot see it, a label above each side that says what kind of thing it is ("Country" above the front, "Capital" above the back), shown with its side whichever way the card is studied, and a note under each side, shown once the answer is revealed (CardContentFields.tsx).

A card's page

#/card, from a card's front in the Browser (CardScreen.tsx, CardContainer.tsx). It shows the card as study shows it, then its editor: the same fields as the card creator, and, under them, the card's wrong options. Those are the other answers a course shows beside the right one when it asks the card as a multiple-choice question. Each can be edited, retired or deleted, and gets a note on why it is wrong (DistractorFields.tsx); one that the deck's library release published is only ever retired. Hints under them point out an option that lacks a language the back is in, or is in one the back is not, and too few options for a course. Save writes the card and its wrong options at once; "Remove card" asks first, then returns to the Browser. An unknown card falls back to the Browser.

Under the editor, the card's history: where it stands in each direction (its interval, its next review, the day it was first studied) and every answer to it, newest first (statistics.md). The leeches and hardest cards of the statistics link here.

A library deck's cards

Before importing a library deck, a learner can look at it three ways, all read-only:

All three read the release's cards once, from the library (UseCases.listLibraryCards), and share them under one query. A deck added from a link has none of them: it is read only to be added (deck-library.md).

How it is tested