Original source · exact version bafyreiabcc3fhwlaghp6aecfwji4baigcusqo5h6tcf7bkr45nzqy26tga · Read-derived block

Classification: skip; source kind: reference-only; decision: reject; confidence: high; review status: needs-review.

Rationale: Classification follows the source’s stated user-facing intent and content; sparse or exploratory sources remain reviewable rather than being merged or embellished.

Review qualification: Uncertain identity/behavior/duplication remains a separate candidate; do not merge without review.

Evidence snapshot: original readable text and block backlinks

Paragraph   source block

Heading Problem source block

Paragraph Seed has grown from a P2P document publishing tool into a platform where communities and companies build shared knowledge. The current app layout does not make this purpose clear. source block

Paragraph Users do not know where to start, what a site contains, or where to find a tool. They lose context when they move between documents, discussions, versions, activity, notifications, people, explore, and agent sessions. Desktop and web also use different interactions for related tasks. source block

Paragraph The layout must explain the site, make useful starting points clear, and let users bring in related content without disrupting their main task. source block

Heading Solution source block

Paragraph DEMO 👉 https://seed-layout-lab.pages.dev/ source block

Paragraph Use an isolated layout study to choose a common interaction model for desktop, web, and mobile before changing the production apps. Compare two working proposals with the same content and tasks: source block

Paragraph Guided: one main reading area, stable site navigation, and one related panel with adjustable width. No document tabs. Breadcrumbs show location. The omnibar shows recent documents before search results. source block

Paragraph Flexible: the same starting experience, with docked panel groups that users can move, split, resize, close, and focus. Tabs identify open content within groups. Provide menu and keyboard controls as alternatives to dragging. source block

Paragraph Use Guided as the starting direction. Keep the route to a more flexible workspace open, subject to user testing. source block

Paragraph Both proposals include: source block

Paragraph A site home that explains its purpose and offers clear starting documents. source block

Paragraph Small, labelled cues for comments, discussions, connections, and contributors. Open these when requested; keep the source document visible in related panel headers. source block

Paragraph A file browser for the whole site, with a required site name, enough width for deep folders, and retained filter and expansion state. Guided places it in the navigation area; Flexible can dock it beside other panels. source block

Paragraph A light visual style with clear hierarchy, quiet controls, and readable documents. Use Paseo as a visual reference. source block

Paragraph A shared titlebar with site identity, a desktop omnibar, selected-account avatar, and optional panel shortcuts. Keep experiment controls outside the proposed app layout. source block

Paragraph One visible pane on mobile, with an open-panel switcher. Preserve reading position and discussion drafts when changing panels or screen width. Test temporary detail sheets later. source block

Paragraph Contextual entry to agents. Flexible also provides an Agents destination. source block

Paragraph User stories: source block

Paragraph As a new visitor, I can understand the site and find a useful place to start. source block

Paragraph As a reader, I can notice related discussion, inspect it, and return to the same place in my document. source block

Paragraph As a member, I can start a reply and keep it while I move between views. source block

Paragraph As a frequent user, I can return to recent work through the omnibar. source block

Paragraph As an advanced user, I can arrange several panels without forcing this setup on new visitors. source block

Paragraph Interactive examples: Guided and Flexible. source block

Heading Layout screenshots source block

Paragraph Captured from the hosted prototype with the same sample document and discussion. Desktop viewports are 1600 × 1000; mobile viewports are 390 × 844. Images use 2× resolution. The small bar at the top is for experiment controls and is not part of the proposed app. source block

Heading Guided — desktop source block

Image Guided — desktop: Site files in the wide navigation pane, the document in the main reading area, and its discussion in the related panel. The document has no tabs. source block

Original link/embed source block

Paragraph Site files in the wide navigation pane, the document in the main reading area, and its discussion in the related panel. The document has no tabs. source block

Heading Guided — mobile source block

Image Guided — mobile: The same document fills the reading area. Comments, connections, and contributors remain visible as cues. Open panels returns to the discussion. source block

Original link/embed source block

Paragraph The same document fills the reading area. Comments, connections, and contributors remain visible as cues. Open panels returns to the discussion. source block

Heading Flexible — desktop source block

Image Flexible — desktop: Document, discussion, and site files occupy separate docked groups. Tabs identify open content; dividers and panel actions control the arrangement. source block

Original link/embed source block

Paragraph Document, discussion, and site files occupy separate docked groups. Tabs identify open content; dividers and panel actions control the arrangement. source block

Heading Flexible — mobile source block

Image Flexible — mobile: The document is the visible pane. Tabs retain their close controls, and Open panels provides access to the other open content without compressing the desktop grid. source block

Original link/embed source block

Paragraph The document is the visible pane. Tabs retain their close controls, and Open panels provides access to the other open content without compressing the desktop grid. source block

Heading Scope source block

Paragraph The isolated React, Vite, and Tailwind prototype is implemented and hosted on Cloudflare Pages. It uses sample content, the installed resizable-panel library, and the shared Seed mobile panel sheet. It does not connect to Seed services. Automated checks cover panel state, draft and reading-position retention, and desktop, tablet, and mobile flows. These checks do not establish usability. source block

Paragraph Remaining work is incremental. The estimates below are planning allowances, not delivery commitments: source block

Paragraph Prepare comparison tasks — half a day. Define the same visitor, member, and advanced-user tasks for both proposals. Include a deeply nested document, a discussion, and a return to recent work. source block

Paragraph Run a small user comparison — one to two days, plus participant scheduling. Record task completion, wrong turns, recovery, and whether people can name the current site and source document. Include phone use. source block

Paragraph Revise the preferred proposal — one to two days after comparison. Fix the largest navigation and context problems. Keep changes small enough to compare against the prior version. Run desktop and mobile checks again. source block

Paragraph Write the implementation handoff — half to one day after revision. Specify navigation, panel lifecycle, source context, responsive behaviour, keyboard controls, and which existing app state to reuse. Identify desktop/web differences that need a product decision. source block

Paragraph Production integration needs a separate estimate after the preferred layout and state rules are agreed. Reuse Seed's existing recent-document storage; do not introduce a second history system. source block

Heading Rabbit Holes source block

Paragraph A general window manager with overlapping windows, arbitrary tiles, or nested docking rules. source block

Paragraph Saved layouts across devices before the basic reading and return flows are clear. source block

Paragraph Graph views, new knowledge models, or a redesign of comments and discussions during the layout study. source block

Paragraph Full agent workflows, identity flows, or access-control simulation beyond what is needed to assess context. source block

Paragraph Pixel matching reference apps instead of testing Seed tasks. source block

Paragraph Treating automated browser checks as evidence that users understand the interface. source block

Heading No Gos source block

Paragraph Do not change production app code, routes, backend services, or publishing behaviour in this study. source block

Paragraph Do not add document tabs to the Guided proposal at this stage. source block

Paragraph Do not show every tool and panel by default or require users to arrange a workspace before they can read. source block

Paragraph Do not silently change the source of an open related panel when another document is selected. source block

Paragraph Do not lose reading position or drafts during navigation, panel changes, or responsive layout changes. source block

Paragraph Do not hide the site scope of the file browser or treat it as the device filesystem. source block

Paragraph Do not compress a desktop panel grid onto a phone. Use equivalent actions suited to each screen size. source block

Paragraph Do not add new production history storage or cross-device layout sync. source block

Paragraph Do not use real user content, credentials, publishing, notifications, or live agent calls in the prototype. source block