Build journal
NEWCommunity 5 min read

Bookmarks & Saved

Published Jul 10, 2026

Save a lesson for later and it lands on its own page — no more losing a good lesson in a sea of tabs.

Some lessons are worth coming back to. The one that finally made a concept click, the practice set you want to redo before an interview, the reference you keep half-remembering. Bookmarks & Saved gives every lesson a one-tap save and collects everything you keep on a single page at /saved. This is a how-to for learners: by the end you'll be saving lessons, finding them again, and using your saved list as a lightweight personal reading queue.

What you'll need

  • A learner account, signed in. Saving is tied to your profile, so you'll need to be logged in — a bookmark is yours, not a public action.
  • At least one published lesson to save. You save lessons from the learner side of the app (/learn and the lesson viewer), not from the admin console.

That's it. There's nothing to configure and no setup step — the save action is already on every lesson you can read.

How to save a lesson

  1. Open a lesson from /learn. Browse the library or a framework's timeline and click into any published lesson to land in the focused lesson viewer.
  2. Find the save control on the lesson. It's a one-tap action — think of it like a bookmark toggle that lives with the lesson's other actions (alongside things like notes and likes).
  3. Tap it once. The lesson is now saved to your account. Tapping again removes it — the control is a toggle, so the same button saves and un-saves.

You don't leave the page, lose your scroll position, or interrupt your reading. Saving is deliberately low-friction: see something good, tap, keep reading.

Tip: Save while you read, not later. The cheapest moment to bookmark a lesson is the second you realize it's useful — trying to reconstruct "which lesson was that?" from memory an hour later is exactly the problem /saved exists to prevent.

How to find your saved lessons

Everything you've saved lands on its own page at /saved.

  1. Go to /saved (reachable from your navigation). This page is your personal collection — only your bookmarks, no one else's.
  2. Scan the list. Each entry links straight back to the lesson viewer, so getting back into a saved lesson is a single click.
  3. Un-save from either place. Removing the bookmark on the lesson itself, or from the saved list, keeps both views in sync — there's one source of truth for what you've kept.

Because the list is scoped to you and tied to your login, it follows you across sessions and devices. Sign in on another machine and your saved lessons are already there.

Bookmarks vs. notes vs. likes

Praxis924 has a few ways to engage with a lesson, and they're easy to conflate. Here's when to reach for which:

ActionWhat it doesUse it when
Bookmark / SaveAdds the lesson to your private /saved listYou want to come back to this lesson later
NoteAttaches your own text to a section or lessonYou have a thought, question, or reminder to record
LikeSignals the lesson was goodYou want to give the lesson credit

Saving is about retrieval — "get me back here." Notes are about your words on the material, and a like is a public-ish signal of quality. They stack: it's perfectly normal to like a lesson, save it, and leave a note on one section all at once.

When it goes wrong

Most friction here comes from being logged out or looking in the wrong place.

SymptomLikely causeFix
No save control on the lessonYou're viewing as a guest, or it's an unpublished draftSign in; make sure the lesson is published
/saved is empty after savingYou saved while signed out, or under a different accountConfirm you're logged into the same account, then re-save
Saved lesson won't openThe lesson was unpublished or removed after you saved itOnly published lessons are readable; ask an admin if it should be live
Tapped save but nothing changedTransient network hiccup on the toggleTap again and confirm the state; refresh /saved

Note: A bookmark points at a lesson — it doesn't freeze a copy. If an admin edits or regenerates that lesson later, your saved entry shows the current version. That's usually what you want (you get the improved content), but it does mean saved content can change under you.

What you get

A one-tap habit and a page that pays it back. Once saving is muscle memory, /saved becomes a genuine study tool: a pre-interview review queue, a shortlist of the lessons you want to redo in /practice, or just a way to not lose the good one you found at 11pm. Concrete next moves:

  • Build a review queue: save the lessons you want to revisit, then work /saved top to bottom before a mock interview.
  • Pair it with progress: save lessons you haven't finished so an incomplete one never falls off your radar.
  • Combine with notes: save the lesson, drop a note on the section you struggled with, and your future self arrives with both the material and your own reminder waiting.
Published in build journal