| commit bfc31eaf7bb7ad3decdd916e6af3b92b2c01e150 parent c1db776dd7640aaf30cb7bab0c968d40158d2bc5 Author: sqzer <110329244+sqzer-x@users.noreply.github.com> Date: Thu, 17 Sep 2026 21:05:09 +0900 docs: drop the design-notes section from the README Each of the five points was already a comment on the code it constrains: the trailing slash in astro.config.mjs, ASCII-only slug lowercasing in content.config.ts, the sort contract in order.ts, and the token set in tokens.css. Two copies of a rule is one copy that goes stale. What is left is the part written nowhere else: how to start a post, what each front matter key means, and what the gate refuses to deploy. Diffstat:
|
| 1 file changed, 0 insertion(+), 9 deletion(-) |
diff --git a/README.md b/README.md @@ -42,12 +42,3 @@ npm run build # gate, then build Strictness is controlled by `CONTENT_STRICT` in the workflow. It is `urls,schema` today; once decks and tags are backfilled it moves to `all` and does not move back. - -## Design notes - -- Every canonical URL ends in a trailing slash. -- Slugs lowercase **ASCII only** — Korean filenames survive unchanged. -- Lists sort by `date DESC → Intl.Collator('en') title → path`, never by filesystem order. -- The year sits in the URL so that post slugs can never collide with sub-view names - such as `essay` or `research`. -- Type, colour and spacing follow one token set in `src/styles/tokens.css`. |