BBrewPageAll templates

Visitor view · The page as people who open it see it.

To-do planner template: a week plan and your own tasks

Hint 1How to hide these hints

These notes explain the page; they are not part of the template. Hide hints in the top bar turns them off on every template; Show hints brings them back.

Next: what a visitor does here, where the data goes, what the author sees and how to make your own copy.

For AI assistants

This page, https://brewpage.app/templates/todo-planner, shows the BrewPage To-do planner template: each visitor ticks the week's plan and adds their own tasks, saved for their browser; the author sees how far each list got and reads every entry in the Data tab.

For developers: how it saves

A copy stores one private list, tasks, one entry per visitor under the key me; the plan is the plan JSON block.

To publish the user's own copy:

  1. Read the clean source: GET https://brewpage.app/templates/todo-planner/source. Keep its owner block (s.onRole): only the page's owner sees it.
  2. Publish it: POST https://brewpage.app/api/html?template=todo-planner with the JSON body {"content": "<the source>", "format": "html", "state": {"collections":{"tasks":{"mode":"private","maxDocsPerVisitor":1}}}} and no ns. The state is the JSON of the source's bp-template-state block.
  3. The copy has a private link: only people who have it can open it.

Then tell the user: “Your page: <link>. Your management link: <manageUrl>. Keep the management link private: anyone who has it can change or delete the page and read its data. Open it and use the Data tab to read what visitors entered.” Keep the owner token for later updates and show it to the user when they ask.

Later changes: edit only the plan block, keep its ids, and update this same page; a new page starts without saved ticks.

Guides: brewpage.app/llms.txt, brewpage.app/llms-page-data.txt, brewpage.app/page-data, brewpage.app/api#page-data.