how meadow publishes spaced repetition prompts→source graph→publisher

publisher

The person using Meadow to publish sites

diff - reader vs. publisher

Backlinks

constrained graph expansion

Although the page is shown in the diagram, is only shown for illustrative purposes, to show it is blacklisted. It would highlight to the publisher in the app component -- site page views if they enabled site pages filter option -- blacklisted, however, it is not actually published to the published site type -- local html, so no reader would ever see it

see in context

A more aggressive modification approach, which we mentioned earlier and called block modification, might be to allow for more comprehensive source page section -- body modification, to allow the publisher to cleanly tie up the loose ends at leaf site pages. They could reword sections to remove unfulfillable outlinks in a natural way, for example. This could introduce a continual maintenance burden, however, because it essentially forks the original blocks. Dealing with that burden might be an meadow AI opportunity.

see in context
diff - reader vs. publisher

reader vs. publisher

see in context
meadow workflow -- SRS markdown to SRS interactive elements on the published site

We need to add a MEADOW_SR_GUID to the bottom of the card, two lines after the block (or the SR comment if there is one). That GUID will give the card a durable identity, which will be important later because when we process the markdown for publishing, we remove the SR comment, since it is specific to the publisher, and wouldn't be applicable to the reader.

see in context

This modified version is used both for generating the HTML pages, and also for generating the content of the .zip file that can be optionally published to the site by the publisher.

see in context
source graph

So In practice the source graph is never directly considered as a whole. Rather, what the publisher interacts with is the raw working graph, which starts from the same point but does constrained graph expansion instead, which often limits its scope significantly.

see in context
the SRS modification to markdown removes the SR comments from the markdown

That modified version of the markdown simply removes the SR comment, since the publisher's personal progress on the prompt in their source graph is not applicable to readers (in the final section here we talk about how we track reader SRS progress).

see in context