# a4list > Track your daily habits and targets with pen and paper. > > A single A4 sheet folds into four A6 segments. > > Use 14 checkboxes for two weeks or 7 checkboxes for one week on every task. Every task row uses the sheet's checklist setting: either a `7 x 2` series of 14 checkboxes for two weeks or a row of 7 checkboxes for one week. The one-week layout places a blank spacer after the seven daily boxes, followed by an undivided two-box total field at the far right. Daily habits form visible chains, making it easy to see at a glance which habits the user is maintaining and which days they have missed. New sheets default to the 14-box layout. ## Documentation - [API reference](/api.md): Whole-document writes, lifecycle operations, and usage notes. - [a4list plain text](/plain_text_format.md): Compact panel/row syntax, editor mappings, limits, rules, and examples. - [OpenAPI description](/openapi.json): Machine-readable API types and endpoints. ## Creating sheets from chats The API accepts a complete JSON document (`application/json`) or a4list plain text (`text/plain`) in `POST /api/sheet`. A sheet can be read as a4list plain text at `GET /api/sheet/{capability}/txt`. If an LLM environment cannot send an HTTP POST request, construct a clickable homepage URL containing the UTF-8 source as standard or URL-safe base64: ```text https://a4list.enzom.dev/#create_from_json= https://a4list.enzom.dev/#create_from_txt= ``` The browser decodes the fragment, creates the sheet through the API, and redirects the user to its private write URL. JSON must be the document itself, not an API response envelope. Keep generated links compact because browsers and chat clients impose varying URL-length limits. ## App - [Create a new sheet](/): Open the a4list start page on this deployment.