Notes App (delivered under the project name dawn-simple) is a simple personal notes application. A single note taker registers and logs in with a password, then creates, reads, edits, and deletes their own notes. Every note is stored in a real database and persists per user, so the note taker's words wait for them across sessions and devices.
The product intent is calm speed and trust in saved work: a quiet, personal tool with a sharp editorial identity rather than a template dashboard. The audience is one note taker who wants to write something down quickly and know it is kept safely under their own account.
This document is the System Requirements Document for the product. It specifies the required backend API server, the real database with a users table and a notes table, password-authenticated register and login endpoints, and database-backed CRUD endpoints for notes. A frontend-only application is explicitly out of scope.
Notes App is a full-stack web application composed of three provisioned services:
users and notes tables.The only active human actor is the Note taker. The note taker arrives anonymously at the Landing page, establishes or verifies identity on the Login page, and then works with their own notes on the Notes and Note Details pages. The backend and database are non-persona system actors that execute and persist the note taker's work.
Accepted current behavior: self-service registration and password login; creation of notes; viewing the note taker's saved notes; editing saved notes; deleting saved notes; and durable per-user storage of notes in the database.
Narrow exclusions: there is no frontend-only delivery, no note sharing or collaboration, no rich media attachments, and no administrative or role-based controls. Notes are private to the account that created them.
Removed from scope
Dawn Simple is delivered as a first-party web application with application-owned identity. The Landing page is publicly reachable and explains what the app is and who it is for. The Login page is also publicly reachable and is where the note taker either registers a new account or verifies an existing one with a password; it is the anonymous entry boundary for protected work. The Notes and Note Details pages require login and are only reachable after identity is established.
All note data is owned by the backend and persisted in the MariaDB database. The frontend never stores notes as its source of truth; it reads and writes through the backend API. Notes are scoped to the authenticated user, so one account never sees another account's notes.
Everything described in this document is current scope. No future-horizon features are committed.
FR-1 — Register an account (explicit; required_inference for self-service enrollment) As a Note taker, I should be able to register a new account with an email and password on the Login page, so that I have my own private space for notes.
users table with a securely hashed password; the note taker is authenticated and taken to the Notes page.FR-2 — Log in with a password (explicit) As a Note taker, I should be able to log in with my email and password, so that I can reach my own saved notes.
FR-3 — Create a note (explicit) As a Note taker, I should be able to create a note with a title and body, so that I can write something down and keep it.
notes table owned by the authenticated user; the note appears in the note list.FR-4 — View saved notes (explicit) As a Note taker, I should be able to view my saved notes, so that I can find and reread what I wrote.
FR-5 — Edit a saved note (explicit) As a Note taker, I should be able to edit a saved note, so that I can correct or extend what I wrote.
notes row is updated and its updated timestamp changes; the change is visible on return to Notes.FR-6 — Delete a saved note (explicit) As a Note taker, I should be able to delete a saved note, so that I can remove notes I no longer want.
notes row is removed from the database and the note disappears from the list.FR-7 — Durable per-user storage (explicit) As a Note taker, I should have my notes stored in a real database under my own account, so that they persist across sessions and are never mixed with another user's notes.
notes table holds the note with a foreign key to the owning users row; every read is filtered by the authenticated user.FR-8 — Real backend API with register and login endpoints (explicit) As a Note taker, I should have my registration and login handled by a real backend API server, so that authentication is genuine and not simulated in the browser.
FR-9 — CRUD API endpoints for notes (explicit) As a Note taker, I should have my note operations served by database-backed CRUD endpoints, so that every action I take is actually saved.
notes table and returns the result.users table.notes table owned by the new user.notes row and its updated timestamp.notes row from the database.The creative direction is authoritative: editorial confidence for a quiet notes tool, after Tobias van Schneider — huge type, warm paper, one hot accent, no clutter.
Palette (light mode)
#F4EFE6 (warm off-white paper ground, ~70% of the page)#FFFDF8#141312 (ink black)#141312 (ink black for type and rules)#E2401B (vermilion — primary action, active note tab, one headline word only)#7A736ATypography
Shape language
Layout
Imagery
Avoid: blue or indigo accents, violet gradients, rounded card grids with hover lift, Inter/Roboto/system-ui fonts, centred hero with pill button, drop shadows, glass panels.
The public entry is a warm paper ground with a 128px Fraunces headline set flush left across 9 of 12 columns: "Write it down. Keep it yours." — with the word "yours" in vermilion #E2401B. A thin ink rule runs under the headline, and the CTA "Start a note" sits as a small black bar at the left edge of that rule. Below the promise, a full-bleed ink-black band separates the landing statement from the login entry, carrying the subline "Dawn Simple saves every note to your own account, so your words wait for you." and the login link in white type. The note list on the Notes page echoes the same ruled-index language: rows ruled with hairline ink lines, dates in a narrow left column, and the active note tab shown as a solid vermilion block with white type.
Interaction Model: Animated Motion Tempo: restrained Hero Dimensionality: flat
Landing Hero Motion Brief
users table and a notes table.clamp()) to fit; no element covers readable text or controls. Decoration and imagery may bleed or crop instead.prefers-reduced-motion, provide a usable static arrangement of all content.users and notes tables.frontend, backend, and database — wired together; the frontend calls the backend, and the backend connects to the database.notes table.#E2401B, used only on the primary action, the active note tab, and one headline word.
Dawn Simple
Dawn Simple saves every note to your own account, so your words wait for you.
What Dawn Simple does
Dawn Simple is a personal notes tool for one note taker: calm speed, no clutter, and every note held under your own account.

Dawn Simple
Dawn Simple saves every note to your own account, so your words wait for you.
What Dawn Simple does
Dawn Simple is a personal notes tool for one note taker: calm speed, no clutter, and every note held under your own account.
No comments yet. Be the first!