Make a journal, step by step

1Open the editor1 min

The editor is a web page. You can try it with sample data first, then open your own copy.

There are three ways in. Pick one:

• Try the demo. Open the editor demo. It has a sample book called Northlight. Nothing you do is saved anywhere, so you cannot break it.
• Your own copy on the web. If you set up the project's site (see SETUP.md), your working editor is at /app/ on that site. It saves in your browser and can commit to your repository.
• On your computer. It is one file with no server. Needs Node 20 or newer.

cd journal && npm ci
KW_PROFILE=content/profile.example.json KW_OUT=out-sample node render.mjs month 2026-10 test.ics
KW_PROFILE=content/profile.example.json KW_OUT=out-sample node editor/build.mjs
# then open journal/editor/dist/site/index.html in your browser

The editor has five zoom levels. You move between them with one row of buttons, and you can always tell where you are from the breadcrumb.

2Choose a profile and a trim3 min

The profile is who and where the book is for. The trim is the paper size. Both are set once and every page follows them.

A profile is one small file, journal/content/profile.json: your name, the book title, where you live (for the sun and moon), your time zone, when your day starts and which trim to print. Nothing personal lives in the code. To start your own, the quickest way is the setup command in chapter 3, which asks the questions and writes the file. Or copy the generic example and edit it:

cp journal/content/profile.example.json journal/content/profile.json

{
 "person": { "name": "Sam" },
 "book": { "title": "Northlight", "start": "2026-10", "edition": 1 },
 "location": { "place": "Lakemont, MN", "timezone": "America/Chicago" },
 "day_start_hour": 5,
 "trim": "small"
}

The editor shows the same facts as a sheet you can change without editing a file. Switch to edit mode on the Book view, then open Book settings.

Trim is the printed page size. KDP in the US offers 5.5 by 8.5 inches and 8.5 by 11 inches (A5 is not offered). A paperback needs 24 to 110 pages. A hardcover needs at least 75 pages on KDP, and this tool builds at least 76 so the count stays even. The top bar switches the preview between the two. The print follows the same choice.

3Start your own book and add packs10 min

One command asks a few questions, writes your profile and builds a sample book. Packs are the folders that hold regional facts, such as support numbers.

This chapter is the command line. The editor has no screen for it, so there are no pictures to press: every step is a command and what it prints. You need Node 20 or newer (CI uses 22), Python 3 with pillow, and Chromium.

git clone <this repository> && cd Journaling/journal
npm ci && npx playwright-core install chromium && pip install pillow
npm run init

npm run init asks the questions below. Every one has a default: press Enter to take it.

• Name, book title, subtitle. Used on the title page, the cover, the spine and in file names.
• Where you are. Pick a city from a short list, or type a place with its latitude, longitude and time zone. It sets sunrise and sunset, the moon, the seasons and the time zone on every clock time.
• The hour your day starts. A whole number from 0 to 8. With 5, 2 a.m. still belongs to yesterday.
• Trim. small (5.5 by 8.5) or letter (8.5 by 11).
• Modules. The moon and sky pages, spoons, therapy blocks and, if your pack has them, trans support and bus pages.
• Content pack. Which pack fills the Support page. generic is the start.
• Book scope and first month. One month per book, a quarter, a season, half a year, a year, your own dates, or an undated book.

When it finishes it has written content/profile.json (it never overwrites one without asking), made your book id and built a sample book from the made-up calendar test.ics. The id is eight characters, different for every book, and it keeps your scan codes apart from every other book's. The end of a run looks like this (shortened):

Wrote content/profile.json (book id 92W8QJHR: it keeps your scan codes apart from every other book's).
Building a sample book from test.ics (about a minute)...
book 2026-10: 2026-10-01 -> 2026-10-31, 5 weeks, 72 pages
Overflow check: [] 0 (every page fits)
Sample book: out-sample/m2026-10/northlight-2026-10-interior-5.5x8.5.pdf (in this folder)

Open that PDF. Every page is the same shape as your real one will be. Then init lists what to do next: put your own calendar in private/ (it is git-ignored and never uploaded), build with node render.mjs month 2026-10 private/your.ics, and open the editor.

Without a keyboard

Every question is also a flag, so init runs in a script or a scratch folder. --yes takes the default for anything you did not give and never asks.

npm run init -- --yes --name Sam --title "Northlight" --city chicago --modules sky,spoons --scope month --start 2026-10
node init.mjs --help          # every flag; --city list shows the built-in places

Packs

A pack is a folder of data that a book reads: a region's support numbers, a transit feed, extra holidays, a table of seasons, word lists for puzzles. The engine holds nothing regional, a pack does, and a pack is only data: nothing in it runs. The one that ships for general use is generic. It has two United States lines, each with a dated source, and a placeholder that prints "Add your local numbers here". The engine never fills in a phone number for you.

The kinds of pack, each with one data file:

• support, trans-support and clinic: support, trans and clinic contacts. These are personal: they never go into a Studio version, fork or proposal.
• transit: a transit agency's schedules. holidays: extra observances. seasons-history: the 72 micro-seasons. puzzles: word lists for the puzzle blocks (chapter 10). These are public.
• region: a bundle of any of the above for one place.

Make one from a starter, seal it, check it, then name it in your profile:

node packs-cli.mjs new support my-town        # copies packs/_template/support/ to packs/my-town/
# edit packs/my-town/support.json
node packs-cli.mjs seal my-town               # records the sha256 of each file in pack.json
node packs-cli.mjs check my-town              # every check; fix what it reports
# then in content/profile.json:   "paths": { "support": "my-town" }

Sealing matters: seal records a hash for each file, and the build stops if a file no longer matches, so a reprint uses exactly what you checked. Change a file, run seal again. node packs-cli.mjs kinds prints every kind's data format and how the build uses it.

The verification rule. The build refuses to print support, trans support or clinic pages when any item has no verification note: "verified": {"who", "date", "source"}, with the date as YYYY-MM-DD and the source the organisation's own page. An item can instead be a placeholder, or say it is unchecked on purpose ("verified": false with "checkBeforePrinting": true), in which case the build prints it and warns you every time. Re-check every number before each print run: numbers and hours change.

4Build a day page from blocks5 min

A day page is a stack of blocks. You choose the blocks, the order and the options. The preview is the real page.

Open a day: press the Day button, or press a page twice in the Book view. A day page opens read-only, so you cannot change it by accident.

Press Edit. The screen splits into three areas.

The header (date, title and tags) shows a small padlock. It is fixed on purpose, so the scanner and the app can always find it.

Add a block

Reorder, hide and remove

Set a block's options

Each block lists its own choices: how many lines, how tall, which rows, which words. The block's name or the small arrow opens them.

Start from a method

You do not have to start with a blank list. The editor has ready-made arrangements built from the methods library (bullet journal, time blocking, a care check-in and others). The result is just blocks, so you can change any of it.

Changed your mind

On a phone

On a narrow screen the preview comes first and the blocks live in a sheet at the bottom. Everything above works the same, with large touch targets.

The same blocks build more than the day page. A day can cover a whole spread (chapter 8), Notes, blank and Collection pages are made of blocks (chapter 9), and the Puzzles group adds a word search and a crossword (chapter 10).

5Size blocks on the grid4 min

Flow mode stacks blocks for you. Grid mode lets you put each one exactly where you want it and choose its size.

Use Flow first. Switch to Grid when you want two blocks side by side, a tall sketch box, or a narrow column of check-ins next to a wide writing area.

The page is a grid of 4 columns by 24 rows. Blocks snap to it, so nothing overlaps and nothing hangs off the edge.

Open a block in the list. In Grid mode it has four steppers.

Drag works too: grab a block on the preview and drop it where you want it. The writing-space number at the top tells you what is left. If a change would push a block off the page, the editor says why and does not apply it.

6Organise pages in the Book view5 min

The Book view shows the whole book. Use it to find a page, to see the order, and to move, hide or add pages.

Press Book in the zoom row. Every page is drawn where it prints, in facing spreads. Page 1 sits alone on the right, like a real book.

Press Spread for two facing pages at reading size. Press Day to edit a day page.

Move, hide, add and remove pages

Press Edit on the Book view. A Pages panel opens with the page count and a check against the KDP limits.

Press a page to select it. A toolbar appears under the canvas.

The panel also asks which months a change applies to: all of them, or one. Use Only when one month needs an extra page and the others do not.

7Library, series and your own titles6 min

Two levels sit above the Book: the Library, where all your books live, and a Series, a set of books that share defaults and a number order.

Press Library in the zoom row (or L). You see a shelf of covers. A series is drawn as a stack. A book on its own is a single cover. The covers are the real title page of each book.

Press a cover to open it. A series opens to its books in order, as Book 1, Book 2 and so on. A library with only one book skips the shelf and opens straight to the book; the Library button still shows the shelf. A book that is on its own has no Series level above it.

Edit the shelf

Press Edit. The toolbar gains the buttons below, and every cover gets its own controls.

Give a book its own title

Press a book's Settings button. A sheet opens at the side (at the bottom on a phone). A book has its own title, subtitle and spine title, so a book in a series does not have to carry the series name. The sheet also holds the series it belongs to, its length, first month, edition, cover style and modules. A setting you leave alone says where it comes from: "Same as the series (Season)" or "Same as the default (1)". Press Save, or Cancel to change nothing.

The cover redraws with the new title, and the series line, "Book 1 of 3 in Season journals", comes from the book's place in the series.

Series defaults

Press a series' Settings button. The sheet holds the series title and subtitle, its books in order (use the arrows, or drag the grip; the order is the numbering), and the defaults every book takes unless it sets its own: length, Keeper, closing page, edition, cover style and which modules are on. Two checkboxes put the series line on the cover and on the title page.

Duplicate makes a copy (a series copy brings a copy of each of its books). Delete always asks first: for a series you choose to keep its books or delete them too. Undo, in the toolbar or in the bar at the bottom, takes a delete back; it holds the last 40 changes.

Where it is kept

• In your browser. With no account, the library lives in this browser. If the browser blocks storage, the editor says "This browser can't keep your library (its storage is blocked). Export it from Edit mode to keep a copy."
• In a file. Export saves library.json. Import checks a file and, after a question, replaces the library. Put the file at journal/content/library.json and the build reads it: KW_BOOK=<book id> node render.mjs ... builds one book of the library.
• In a Studio project. When you are signed in to one, the library travels with the project's versions (chapter 13).
• In the demo. It starts from a made-up library and saves nothing.

8Days that cover a spread5 min

A day can cover one page, or a whole spread: a left page and a right page treated as one canvas.

Open a day and press Edit (chapter 4). At the top of the block list is a box called This day covers.

1. Press A spread: a left and a right page to make this one day a spread.
2. Or tick Every Wednesday is a spread (it names the weekday of the day you are on) to make every day on that weekday a spread, or Every day is a spread for all of them. The most specific choice wins.
3. Read the note under the choices. It says how many Notes pages were added by themselves and gives the new page count with the KDP check.

The preview becomes a two-page canvas: 8 columns by 24 rows, with the fold after column 4. The two pages are always laid out together, so a spread is always on the grid and the Flow and Grid switch is not shown. Drag a block anywhere on either page, or use its steppers; a block stays wholly on one page and nothing crosses the fold. A move that would break a rule is refused and the editor says why.

What it does to the book

• It opens on a left page. A spread day always starts on a left-hand page, so when the page before ended on the left, a Notes page is added to pad it. Page counts, hardcover padding, volumes and the 110-page limit follow. The KDP note under the choices says whether you are still in range: 24 to 110 pages for a paperback.
• Each page keeps the scan zones. Both pages have their own DATE, TITLE and TAGS header (the right page's date says "cont."), frame, SEND TO strip and page code. The right page's id is day.DATE.cont.
• Your layout is saved with your day layout (daypage.json, as spread) only when it differs from the starting spread: the day on the left and a ruled page on the right. Which days are spreads is saved in the book (book.json), and the Pages panel in the Book view shows it on the Day pages row.
• An undated book honours "every day" only; there are no weekdays or dates to pick.

On a phone

The canvas shows one page at a time, with a Left page and Right page switch above it.

9Notes, blank and Collection pages from blocks5 min

A Notes, blank or Collection page is built from the same blocks as a day page, on a grid of its own.

Three page types are made of blocks. Notes and Collection pages keep the DATE, TITLE and TAGS header at the top and have 4 columns by 24 rows. A blank page has no header, so its grid is 4 columns by 27 rows. Blocks that read a day (the moon and sun, holidays, events, the daily fact, the rotating prompt, the 24-hour line, the week strip) and the SEND TO block are day-page only, so they are not offered. The scan frame, the SEND TO strip and the page code are the page's own and never move.

Add a page

1. Open the Book view and press Edit, then open the Pages panel.
2. Scroll to the bottom of the panel. Under Where, choose the page the new one goes before.
3. Press Add a Notes page or Add a Collection page. The page is added and selected.

A selected page you added gets a toolbar under the canvas with Edit blocks, Duplicate, Remove and a Title box. Pages that came with the book cannot be removed, only hidden; the Notes pages the book adds by itself to keep spreads facing have no controls at all.

Edit its blocks

Press Edit blocks. The page opens in the day page editor: palette, option panels, Flow and Grid, Undo and the writing-space meter all work as in chapter 4. You can also open any Notes, blank or Collection page by pressing Edit on its page view, or with the address #page/<page id>/edit. A Notes or Collection page must keep its Writing space block; a blank page may have none.

Every change is saved into the book, the same place the page organiser saves to. The preview uses sample data. The blank page that comes with the sample book works the same way:

10Puzzles: word search and crossword4 min

Two blocks that draw a puzzle on the page, for paper only.

The Puzzles group in the palette has a Word search and a Crossword. They work on day pages and on the block pages of chapter 9.

Press the + of one. The block joins the list; press its name to open its options.

• Grid size (word search) or Largest grid (crossword). Bigger grids need more of the page.
• Difficulty. Word search: easy hides words across and down, medium adds diagonals, hard adds backwards words. Crossword: fewer short words, more words, or most and longer words.
• Words from. Built-in lists (garden, kitchen, sky and calm), your own puzzles pack, or your own words. For your own words, type them separated by commas; for a crossword write each as word=clue with no commas. With too few usable words the block falls back to a built-in list instead of printing an empty puzzle.
• Seed. The puzzle is made from the page, the block and the seed, so the same page prints the same puzzle every time you reprint. Type a different seed for a different puzzle.
• Show answers prints the solution. Large print makes the cells and letters bigger.

The grids are drawn as shapes and real text, so they print sharp and pass the font check. Each grid has a text description for screen readers and the word list or the clues are ordinary text.

11Set scan options2 min

Every page carries a small code so a scan can tell which page it is. These are the choices that go with it.

The date, title and tags header, the 9 pt frame, the send-to strip and the page code are the scan zones. You can move the code and switch it off, but the zones themselves stay put so a scan always knows where to look.

12Accessibility options5 min

Two print options for the whole book, and what the editor itself does for keyboards, screen readers and low vision.

Print: large print and high-contrast ink

Both are off by default, and with both off the book prints exactly as before. Open the Settings button in the top bar.

• Large print. Small type about 40% bigger (nothing under 8.5 pt, headings less, page titles not at all), taller check boxes, mood marks and rows, 1.5 pt rules, and the writing space ruled at 8.5 mm instead of dots. To make room the day page keeps two action lines and leaves out the "On this day" line. The mood scale has 5 steps, water 6 boxes, meals 3.
• High-contrast ink. Light and mid greys (text, rules, dots, grids, borders) print black or near black, and rules are 2 pt. Fills stay, and nothing is lighter than before.
• It never moves the scan zones: the DATE, TITLE and TAGS header, the border, the SEND TO strip and the page code stay as they are. Both work on 5.5 by 8.5 and on 8.5 by 11, and the choice is stored with your layout (daypage.json, print) or in the profile (print).

The preview changes as soon as you switch one on.

In the editor

• Keyboard. Every control can be reached with Tab and shows an outline where you are. A block's grip moves it with the Up and Down arrows. E edits, Esc goes up a level or finishes editing, Alt+Up and Alt+Down change level, Ctrl+Z undoes.
• Screen readers. Controls have names. Changing level announces "Now at: ..." and moves focus to the current crumb. A warning such as "Too full" is announced once when it appears. The puzzle grids carry a text description.
• Touch. Controls are 44 pixels or more, with one known exception below. At 390 pixels wide the page does not scroll sideways.
• Colour and motion. Light and dark follow your device. A "more contrast" setting on the device strengthens the colours. If you asked for reduced motion, level changes and drag animations are instant.
• Language. The editor is in English only today. Its words are all in one catalog, ready for translation, but there is no language switcher yet.

The project checks the editor with an automated test (journal/editor/test-a11y.mjs: axe, target sizes, reflow, focus, announcements, reduced motion). It lists three known gaps: the Blocks, + Add and Preview tabs on a phone do not move with the arrow keys; a block moved by keyboard in Grid mode is not announced; and one-row blocks in Grid mode are 21 pixels tall (the grid cell is the layout), though the steppers and the keyboard do the same job.

The X4 has its own text size and contrast settings (chapter 16).

13Save, share and keep versions4 min

Your work is kept in your browser. Download it when you want a copy, and save a version when you want to be able to go back.

The editor saves a draft in your browser as you work. A download is a copy you can keep, email or load on another computer.

A version is a named snapshot with a message. Use them like save points. They work with no account: until you sign in to a Studio server, they live in your browser.

Save a second version after you change something, then compare the two.

If you sign in to a Studio server (studio/README.md), the same drawer also gives you branches, forks and proposals, so more than one person can work on a book. Private pages, calendars and profile secrets are never put in a version. A named, frozen copy of a version is a release (chapter 14).

14Releases and reusable pages4 min

A release is a named, frozen copy of a saved version, so a printed book can always be traced back to what it was made from.

Releases need a Studio server and a project on it (chapter 13). The public demo and a guest's browser-only versions have none: until you open a server project the Releases section is not shown. To try it, build the editor (chapter 1), run cd studio && npm start (Node 22.13 or newer, nothing to install) and open http://127.0.0.1:8787/. Press Versions, create an account, then choose New project on my account (or Move it to my account). You are that project's owner.

1. Save a version of the book first (chapter 13). A release is made from the latest saved version, never from your unsaved draft.
2. In the Releases section of the Versions drawer, type a Release name, such as v1.0, and optional Notes.
3. Press Release the latest saved version. A name that already exists is refused with the server's reason, and nothing changes.
4. Press a release's download button to save release-NAME.json.

Only a project's owner can make a release. Anyone who can read the project sees the list and can download one, and for a public project that includes people with no account. A release never changes: the server refuses to edit or delete one. It holds the commit, the print settings, public pack references and a manifest with the hash of the two files the build reads (content/book.json and daypage.json), so a later build can be proven to come from exactly that release. Before it is made, the server checks that nothing private is in it, and if it finds something, nothing is written.

Reusable pages

The Studio also keeps a personal library of reusable pages and block layouts, which can be inserted into a book by copy, with attribution and a link to the version they came from. This has no screen in the editor yet. It is only in the server's programming interface (/api/library and /api/projects/:id/insert), so there is nothing to press in the Versions drawer. Protected pages, module pages and private content are refused, and inserting a layout into a Grid day layout is refused. Details and the list of limits are in studio/README.md.

15Export a KDP-ready PDF10 min

The build writes an interior and a cover that pass the checks Amazon KDP asks for. The editor does not print: the build does.

Build one month with the sample calendar. For your own book, replace test.ics with your calendar files (they stay on your computer and are never committed).

cd journal
node render.mjs month 2026-10 test.ics          # 5.5x8.5 interior, into out/m2026-10/
SIZE=letter node render.mjs month 2026-10 test.ics   # 8.5x11, into out/m2026-10-letter/
node cover.mjs month 2026-10                      # the wrap-around cover, sized to the page count

Or build every month and both sizes at once with ./build-all.sh.

Check before you upload. These are the same checks the project runs on every build:

node check.mjs m2026-10               # must print [] 0: no page overflows
pdffonts out/m2026-10/*interior*.pdf | grep "Type 3"   # must print nothing: KDP rejects Type 3 fonts
pdfinfo out/m2026-10/*interior*.pdf | grep Pages        # even; paperback 24 to 110, hardcover 76 or more

• Overflow: [] 0 means every page fits. Anything else lists the page numbers that spill.
• Fonts: no Type 3 fonts. Emoji and odd glyphs are drawn as shapes, so there should be none.
• Pages: an even count in the KDP range. The Pages panel in the Book view shows this too.

Then, on KDP:

1. Sign in at kdp.amazon.com, press Create, then Paperback.
2. Fill in the details. Choose black and white interior, white paper, the trim you built, and no bleed.
3. Upload the interior PDF as the manuscript and the cover PDF as the cover.
4. Open the previewer and look at every page before you order a proof.

16Optional: the X4 e-ink companionoptional

A small e-ink device that shows today and takes button check-ins, with no phone, no feed and no notifications.

The Xteink X4 runs the project's firmware. It shows today on its sleep screen, takes check-ins with its buttons, has a focus timer, and keeps everything on its SD card. Nothing leaves the device except over its own Wi-Fi hotspot, or an explicit sync you start on the device.

Four of its screens, in the order you meet them:

Settings are on the device: text size, contrast and button layout. To move files, open Wi-Fi and choose Hotspot. The X4 makes its own network. Join it from a phone to set the clock, download your logs and upload new books. The radio is off until you pick a row, and it goes off again when you leave the screen. Sync with Studio sends your check-in log to your own Studio account, only when you press Send. It needs the separate x4-tls firmware build: the default image shows the row, says so, and sends nothing. Sync is built but untested on real hardware.

The build makes an X4 EPUB for each month (python3 epub.py m2026-10) and the SD-card files. Setup and the firmware build are in x4/README.md.

17When something goes wrongas needed

The messages you can meet, what each one means and what to press. They are the real wording from the editor and the build.

A page overflows

In the editor, the writing space number at the top of the preview warns in three steps: Getting tight, Too full for busy days and Too full: the page overflows. Switch something off or shorten a block. It reads a busy sample day, so judge by the message, not only the number.

1. Switch the block you can live without off with its switch (it keeps its settings), or remove it.
2. Or shorten a block: fewer lines, a smaller grid, fewer rows.
3. In Grid mode, if you add a block with no room, the editor says "No room for NAME: added switched off. Free some rows, then switch it on."

The print build checks every page again. node check.mjs m2026-10 prints a list and a count. [] 0 means every page fits. Anything else names pages, and the build stops (CI fails). Each entry looks like {"n":41,"over":true,"out":2}:

• n: the page number, counting from 1 at the front.
• over: the page content spills past the page. out: how many elements sit outside the margins.
• cell: bus grid or summary cells whose text is wider than the column. clip: month-calendar cells or week rows that clip their text.
• blk: the names of Grid blocks that clip their content, for example "blk":["checks"]. That is the block to shorten or move.
• scan: parts of the scan strip overlap or spill, for example after a bigger page code.

A busy calendar does not overflow a page by itself: month cells and week rows cap at a few lines and say "+N more".

The X4 has room for 16 custom check-in items. Past that the editor says "X4 holds 16 custom items; you have N. The last M stay on paper."

The 110-page limit

The Pages panel in the Book view counts the pages and checks them against KDP: 24 to 110 pages for a paperback, 76 or more for a hardcover in this tool. Past the limit it says so in red, with the volume plan.

• Over: "112 pages is over the 110-page limit for one printed book. The plan would split it into about 2 volumes; take pages out or hide some to keep one book." Hide pages with the eye, remove pages you added, or let it split: node render.mjs plan private/main.ics shows how many volumes you get, and each volume is its own KDP upload.
• Under: "N pages is under the 24-page minimum for a paperback." (76 for a hardcover). The build pads with Notes pages by itself so the count is even and reaches the minimum; HARDCOVER=1 pads to 76.
• A spread day, extra Notes pages and the "Count as a hardcover" switch all change the count. The note under "This day covers" shows it as you go.

A page would point to nothing

Some pages say "see page N". Page numbers and those pointers follow the pages when they move. If a change would remove a page that another page points to, the editor stops and asks: A page would point to nothing, then "NAME points to NAME, which the book would no longer have." The build refuses such a book, so it cannot be saved or printed until you put that page back. Cancel keeps the book as it was, Apply anyway is for when you mean it, and Undo brings the page back at any time. If a book has already been saved this way, the editor says "Not saved: NAME points to NAME, which isn't in the book. Put it back, or undo." and the build says:

Page "Closing the month" points to page "support", which this book doesn't have. Put that page back or remove the pointer.

In the current page set, a page prints a pointer only when its target exists, and Support, My safety plan and Closing the month cannot be hidden ("Support can be moved but not hidden"), so you should rarely meet this. It guards books you edit by hand and pages added later.

The editor does not load, or the canvas is empty

The editor loads its drag-and-drop helper (SortableJS 1.15.2) from cdnjs.cloudflare.com. If your browser cannot reach it, because you are offline or the address is blocked, the page shows its top bar and then nothing is drawn: the Book canvas stays empty and the editor says nothing. Only the browser console says Sortable is not defined. Your saved work is untouched, because the editor never opened it. Get online (or allow that address) and reload. The editor does not carry its own copy yet. The project's own screenshot scripts take a local copy through SORTABLE_JS, and that is for testing, not for using the editor.

A jump to a page that is not there is refused in words, as above, and nothing moves.

Common messages

• "This browser can't keep your library (its storage is blocked)" or "This browser can't keep versions": a private window or a privacy setting blocks storage. The editor still works for this visit. Use Export and Download to keep a copy.
• "Demo: not saved anywhere": you are in the public demo. Nothing is saved. Open your own copy (chapter 1).
• "That file isn't a day page layout.": Import was given a file that is not a daypage.json. "Couldn't copy here. Use Download instead.": the browser would not give the editor the clipboard.
• "Couldn't reach GitHub." or "Couldn't save. Try again in a moment": the working editor could not commit. Check your connection and your token.
• "Not autosaved: ..." in the Versions drawer: the draft could not be saved to the Studio server; the reason follows.
• "NAME is not a valid profile", with a list: content/profile.json has a wrong field, for example trim: is required: "small" (5.5x8.5) or "letter" (8.5x11), got "a5". Each line names the field and what it needs.
• "Not printing the Support pages of pack NAME: N items have no verification note": give each item a verified note (chapter 3). node packs-cli.mjs check NAME finds it earlier.
• "support.json: changed since it was sealed": a pack file changed after seal. Check the change, then run node packs-cli.mjs seal NAME.
• "No pack ... Installed packs: ...": the id or folder you named has no pack.json. For a folder, give the whole path.
• "KW_BOOK ... is not a book in the library": the book id is not in content/library.json; the message lists the ids that are.
• "Not overwriting ..." from npm run init: a profile is already there. Use --profile for another file or --force to replace it.