Wiki page frame, reader and editor #58

New Issue

2026-07-28T08:10:39Z

archvillainette commented

2026-07-28 08:10:39 +00:00

Part of #47

Question

What is the wiki page frame?

The wiki is where players will actually spend reading time, and _wiki-prose.scss is 1700 lines — over a quarter of the themes SCSS — with two of the last five commits fixing wiki layout (table-of-contents drift, prose alignment). It is a surface being fought with rather than designed.

In scope is the frame, not the prose internals: article column, table of contents, page header and breadcrumb, section landing pages. Every decision here is verified in the TipTap editor as well as the reader, per the parity contract.

Resolve:

Article column width and how it sits against the rails, including pages with no table of contents — the case that has already drifted once.
Table of contents: placement, sticky behaviour, behaviour when short, absent, or very long, and what happens on narrow screens.
Page header anatomy: title, breadcrumb, namespace, last-edited, edit affordance — composed from the named ornament components.
Section landing pages: what a namespace or section index looks like, since it is a directory rather than an article.
Which of the 1700 lines the frame decision makes redundant. Some of that file is almost certainly layout patching that a real frame removes; naming those blocks is part of the answer, deleting them is not this maps job.
The parity check, run on both reader and editor in the live stack before this ticket resolves.

Prototype on a throwaway branch, link it here.

Part of #47 ## Question What is the wiki page frame? The wiki is where players will actually spend reading time, and `_wiki-prose.scss` is 1700 lines — over a quarter of the themes SCSS — with two of the last five commits fixing wiki layout (table-of-contents drift, prose alignment). It is a surface being fought with rather than designed. In scope is the **frame**, not the prose internals: article column, table of contents, page header and breadcrumb, section landing pages. Every decision here is verified in the TipTap editor as well as the reader, per the parity contract. Resolve: - Article column width and how it sits against the rails, including pages with no table of contents — the case that has already drifted once. - Table of contents: placement, sticky behaviour, behaviour when short, absent, or very long, and what happens on narrow screens. - Page header anatomy: title, breadcrumb, namespace, last-edited, edit affordance — composed from the named ornament components. - Section landing pages: what a namespace or section index looks like, since it is a directory rather than an article. - Which of the 1700 lines the frame decision makes redundant. Some of that file is almost certainly layout patching that a real frame removes; naming those blocks is part of the answer, deleting them is not this maps job. - The parity check, run on both reader and editor in the live stack before this ticket resolves. Prototype on a throwaway branch, link it here.

archvillainette added the wayfinder:prototype label 2026-07-28 08:10:39 +00:00

archvillainette added a new dependency 2026-07-28 08:10:55 +00:00

#52 Wiki reader and editor parity contract

archvillainette added a new dependency 2026-07-28 08:10:55 +00:00

#54 The ornament and frame component set

archvillainette added a new dependency 2026-07-28 08:10:55 +00:00

#56 Page width and density system

archvillainette referenced this issue

2026-07-28 08:11:24 +00:00

Wayfinder: Westgate palette re-tune and game-site structure #47

archvillainette referenced this issue

2026-07-28 08:50:47 +00:00