From c704a75895606d4a57071e7efade8f5898c84fc5 Mon Sep 17 00:00:00 2001 From: Will Kahn-Greene Date: Fri, 25 Sep 2026 09:19:55 -0400 Subject: [PATCH] docs: record create's default page width as an L9 exception Closes #184. create gives a new page page_width max when nothing declares one, and update leaves an undeclared width alone. That difference is on purpose: a new page has no width a person set, and markfluence should create good-looking pages, while update may be touching a page someone set up by hand. It goes in L9's Accepts rather than changing either verb. --- docs/design-principles.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/design-principles.md b/docs/design-principles.md index f90697b..456cc48 100644 --- a/docs/design-principles.md +++ b/docs/design-principles.md @@ -357,6 +357,12 @@ value looks exactly like an unfinished edit, so markfluence refuses it. Use the Confluence UI to clear a status. `labels: []` can mean "remove them all", because an empty sequence has its own spelling. +`create` gives a new page a width of `max` when no place declares `page_width` +because WillKG thinks it looks better and markfluence should create +good-looking pages where possible. For `update`, it's a different story where +the user could be updating existing content that wasn't created by markfluence +and we should respect whatever the page width was by default. + ## Conformance ### C1 `preview-compatible-resolution`