> For the complete documentation index, see [llms.txt](https://klassdocs.gitbook.io/klassapp-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://klassdocs.gitbook.io/klassapp-documentation/docs/proposals/2026-10-05-marks-import-ui-1.md). # Screenshots: marks import (demo data only) Taken from the app (rebased on main after #986, so the teacher template is the one from #986) running on SQLite with the Demo Junior School and Demo Senior School seeders, signed in as the demo teacher and the demo admin. Each case imports an edited copy of the downloaded template: some marks changed, one blank, one above 100, one unknown registration number and one row with no registration number. File names: `---.png`, steps: 1 entry point (button), 2 upload, 3 preview (nothing saved), 4 result. Junior cases tick "overwrite"; senior cases leave it unticked, so differing marks are reported as skipped. `metrics.json`: measured in the browser at each width. `buttonHeight` is the entry-point button (44px), and `preview`/`result` `sw` and `iw` are page scroll width and window width (equal means no sideways scroll). The "small" list in `preview` shows controls under 44px: the sidebar links (outside this change) and the 24px checkbox, which sits inside a 44px-tall label. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://klassdocs.gitbook.io/klassapp-documentation/docs/proposals/2026-10-05-marks-import-ui-1.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.