I taught myself web development from free, open textbooks and whatever public courseware I could find. The hardest part was not motivation. It was retention. I would read a chapter on a screen, feel like I understood it, and then a day later it would evaporate.

Digital textbooks are convenient, searchable, and often free, but they also make it easy to slide into passive reading. The fix is not more highlighting. It is a workflow that forces you to think, predict, compress, and retrieve as you read.

A college student sitting at a desk, reading a digital textbook on a tablet and writing brief notes in a notebook beside it, natural indoor light

Start with low-friction setup

If taking notes feels annoying, you will not do it consistently. Before you read, spend two minutes on your environment.

Pick one home for your notes

You have three realistic options. Choose one and stick with it for an entire course.

  • Inside the ebook or PDF using highlights and annotations. Best when the platform has good search and export.
  • A separate notes app (plain text, Markdown, or a document). Best when the book is clunky or you are switching sources.
  • Paper notes alongside the screen. Best when handwriting helps you think and remember.

Mixing all three randomly is the fastest way to lose your best insights.

Use a split-screen routine

My default: textbook on the left, notes on the right. If you are on a phone, do it in passes: read a section, then flip to your notes and write from memory. The extra step is not a drawback. It is a memory feature.

Decide your annotation toolbox

Many digital reading tools offer the same core features: highlight, comment, bookmark, search, and sometimes tags or exports. That is enough. You do not need fancy pens or ten colors. You need consistency. If your platform is missing a feature you want (like exporting highlights), compensate by keeping more of your notes in a separate, searchable place.

If you are still choosing a device or app for etextbooks, I wrote more about hardware tradeoffs here: Are some tablets better than others for etextbooks?

Stop using highlighting as memory

Highlighting feels productive because it creates visual change. But most people highlight far too much, which turns the page into a neon swamp and makes review pointless.

The 10 percent rule

As a personal rule of thumb, I aim to highlight no more than about 10 percent of what I read. It is not a law. It is a speed bump that forces you to choose only what is structurally important.

What to highlight (and what not to)

  • Highlight: definitions in your own words, formulas, laws, cause and effect claims, step lists, and sentences that connect ideas.
  • Do not highlight: examples you can recreate yourself, long explanations, or anything you would not know how to explain to a friend.

Use only two highlight types

If your app supports colors, keep it simple:

  • Color 1: core concepts (the stuff you would put on a one-page cheat sheet).
  • Color 2: testable details (dates, parts, steps, exceptions).

If your app only has one color, that is fine. The strategy still works.

Turn notes into learning prompts

Here is the shift that made digital textbooks work for me: I stopped writing annotations that repeat the book and started writing annotations that force retrieval later.

Write questions, not summaries

When you hit an important paragraph, add a note that asks something like:

  • “Why does this happen?”
  • “What are the steps, in order?”
  • “What would break if this assumption changes?”
  • “How is this different from the previous concept?”

Your future self can answer those questions without rereading the entire chapter. That is the goal.

The 5 note types I use most

  • Explain-it-like-I’m-busy: one sentence you could say out loud in one breath, around 10 to 15 seconds.
  • Process: numbered steps in your own words.
  • Common trap: what learners typically confuse and how to avoid it.
  • Example seed: a short cue to recreate an example from scratch.
  • Bridge: how this connects to something earlier (or another class).

How to handle diagrams, tables, and code

Visuals are where passive reading hides. My move is to turn the graphic into a prompt:

  • Diagrams: cover labels and redraw it from memory, then check. Your note can be: “Redraw the parts of X and label each.”
  • Tables: convert rows into comparisons. Note: “What is the difference between A and B across the three criteria?”
  • Code blocks: do not just reread. Note: “Rewrite this from scratch and change one variable. What breaks?”
A person using a laptop to read an ebook, highlighting a short sentence and typing a brief margin note in the reading app

Use active reading loops

Digital reading often feels fast, especially when you are scrolling, skimming, and searching. That perceived speed can trick you into moving on before your brain has done the work. Here is a loop that keeps you honest.

Loop A: Preview, read, recall

  1. Preview: read headings, bold terms, and any end-of-section questions.
  2. Read: one small chunk (a subsection, not a whole chapter).
  3. Recall: look away from the text and write 3 to 5 bullet points from memory.

The recall step is one of the highest-leverage parts of the whole process. Do not skip it.

Loop B: Teach-back in about 60 seconds

After two or three chunks, record a short voice note or speak out loud: explain what you just learned as if you are helping a friend who missed class. If you get stuck, you just discovered what to review.

Loop C: One problem, one paragraph

For skill-heavy subjects (math, coding, accounting, chemistry), do this:

  • After every key concept, solve one small problem immediately.
  • If the book has no exercises, create one. Change the numbers, tweak the variables, or explain the concept with a fresh example.

Reading without doing is where confidence goes to die.

Build a review layer

The best digital advantage is search. But search only helps if your notes have a structure. I like to add a thin review layer that turns my annotations into an index.

Add a short tag to key notes

Even if your app does not support real tags, you can fake it by starting notes with consistent labels:

  • DEF: definition
  • STEPS: procedure
  • WHY: reasoning or explanation
  • EX: example prompt
  • TRAP: common mistake

Later, you can search “TRAP:” and instantly pull up the pitfalls you flagged while you were learning.

Create chapter-end notes in three lines

At the end of each chapter, write three lines in your notes app or in a final annotation at the top of the chapter:

  1. Big idea: what the chapter is really about.
  2. Must-know list: 5 to 10 items maximum.
  3. Can I do it?: one task you should be able to perform now.

Back up your notes once a week

This is the boring part that saves you. If your notes live in a separate app, do a quick weekly export or sync check so you do not lose a semester of annotations to one broken device.

What changes by format?

Different formats push you toward different strategies. Here is how I adapt.

If you are reading a PDF

  • Bookmarks are your friend. Use them for major sections and problem sets.
  • Keep highlights minimal and rely on question-style annotations.
  • If the PDF text is not searchable, take more notes outside the file so you can search later.

If you are reading a web textbook

  • Expect distractions. Turn off notifications and read in full-screen.
  • Copying and pasting can become a trap. Paraphrase instead.
  • When there are embedded quizzes, treat them as mandatory retrieval practice.

If you are using an ebook app

  • Highlights are easy to overdo. Use the 10 percent rule aggressively.
  • Favor short notes that begin with “Q:” so you can scan them later.
  • Use location markers or bookmarks for “return here” sections.

If you are exploring more digital options, my broader overview is here: Etextbooks.

A workflow for tonight

If you want something concrete, use this on your next chapter. No special apps required.

Step 1: Set an outcome

Write one sentence: “After this session, I should be able to…”

Step 2: Read in small chunks

Pick a chunk you can finish in 5 to 10 minutes. Use Preview, Read, Recall.

Step 3: Annotate what you will test

Highlight sparingly. Add 1 to 3 annotations per chunk, mostly questions and traps.

Step 4: Make a mini review

At the end, write:

  • 3 bullets you remember without looking
  • 1 thing you are confused about
  • 1 practice problem you will do tomorrow

Step 5: Do a quick retrieval check

Tomorrow, spend about 8 minutes answering your own “Q:” annotations and your chapter-end notes. If you can answer them, you are done. If you cannot, you know exactly what to reread.

Common mistakes

“My notes are huge, but I still forget everything.”

Your notes are probably descriptive instead of retrieval-based. Replace summaries with questions and teach-back prompts.

“I highlight because it helps me focus.”

Use highlighting as a reward after you understand a paragraph, not while you are trying to understand it. Read first, then highlight what remains important.

“I cannot concentrate on screens.”

Try the two-pass approach: first pass is skim and structure, second pass is deep reading with recall. Also, consider paper notes alongside the screen, even if the book is digital.

“I never review.”

Then the best strategy is one that bakes review into reading. The Recall step does that. It is review, in real time.

For more general study routines that pair well with digital textbooks, see: Study tips.

Quick checklist

  • I read in small chunks, not whole chapters in one go.
  • I do a recall step from memory every chunk.
  • I highlight under about 10 percent and only what is structurally important.
  • My annotations are mostly questions, steps, traps, and bridges.
  • I write a three-line chapter-end note.
  • I do one short retrieval review the next day.
A quiet study desk with a tablet open to a digital textbook page, a stylus resting nearby, and a cup of tea in the background