Page Hierarchy, Group Pages & Table View

1. Problem Statement

NowPage supports hierarchical URLs via parent_page_id chains, but three capabilities are missing:

1. Group pages are dead ends. To create a URL like /prds/vault, you need a parent page called prds — but that page must have custom HTML. If you don't write content for it, /prds/ is a blank page. Users avoid creating groups because the parent page is wasted effort.
2. The list view is a sketch, not a tool. PageManager.tsx shows page rows with name + status + link. No columns, no sorting, no search, no folder info, no dates. Once you have 30+ pages, the list view is useless and you default to the grid (which is slow to scan at scale).
3. No UX for managing hierarchy. The tree view supports drag-to-reparent, but there's no guided flow for "create a group with children" or "convert a flat page into a group." Users who want domain/group/page/subpage must manually set parent_page_id on each page.

2. Current State

What Exists

What's Missing

3. The Three URL Structures

3.1 Structure Types

3.2 How This Already Works (Routing)

The serve route (app/serve/[[...slug]]/route.ts) already handles all three:

Request: domain.com/prds/vault/appendix
  1. Try full_path = "prds/vault/appendix"  →  match? serve it
  2. Try slug = "prds/vault/appendix"       →  match? serve it
  3. 404

The full_path is built automatically from the parent_page_id chain when a page is created/updated in app/api/pages/route.ts.

4. Auto-Rendering Group Template

4.1 When It Triggers

A page is considered a "group page" when ALL of these are true:

• Has child pages (parent_page_id references to it exist)
• Has no custom HTML content OR has html_content that is empty/placeholder
• OR has hc_type: "group" in its HC metadata (explicit opt-in even with content)

4.2 HC Metadata Extension

{
  "hc_version": "1.3.3",
  "hc_type": "group",
  "title": "Platform PRDs",
  "group_principle": "These PRDs define the NowPage platform build sequence.
                      Each phase unlocks a multiplier on the one before it.",
  "neural_registry": true,
  "child_order": "manual",
  "gate": null
}

New fields:

4.3 Auto-Render Template Design

MasteryMade design system. Same fonts (Bebas Neue / DM Sans / DM Mono), same color palette (cream/ink/amber). The template structure:

4.4 Data Source for Auto-Render

The template renders from child page metadata. No LLM calls, no generation. Pure data assembly:

interface GroupChildData {
  page_name: string        // from pages table
  slug: string             // from pages table
  full_path: string        // from pages table
  description: string      // from HC metadata in html_content (parsed)
  tags: Tag[]              // from page_tags join
  created_at: string       // from pages table
  updated_at: string       // from pages table
  is_published: boolean    // from pages table
  children_count: number   // count of this page's own children
}

4.5 Implementation Location

The auto-render happens in the serve route, not as stored HTML:

// app/serve/[[...slug]]/route.ts

// After finding the page...
if (isGroupPage(page)) {
  const children = await getChildPages(page.id, supabase)
  const metadata = parseHCMetadata(page.html_content)
  const html = renderGroupTemplate({
    title: page.page_name,
    principle: metadata?.group_principle,
    children,
    childOrder: metadata?.child_order || 'manual',
    domain: domain.full_domain,
    groupSlug: page.slug,
    updatedAt: page.updated_at
  })
  return new Response(html, {
    headers: { 'Content-Type': 'text/html' }
  })
}

function isGroupPage(page: Page): boolean {
  const metadata = parseHCMetadata(page.html_content)
  if (metadata?.hc_type === 'group') return true
  if (!page.html_content || page.html_content.trim().length < 100) {
    // Check if it has children
    return true  // caller must verify children exist
  }
  return false
}

4.6 Group Page with Custom Content

If a group page has hc_type: "group" AND substantial html_content, serve the custom HTML. The auto-render is a fallback for empty groups, not a replacement for authored content. This means:

• You CAN write a custom group page (like the command center) and it takes priority
• You CAN leave a group page empty and get a useful auto-rendered index
• The hc_type: "group" flag controls neural registry behavior regardless of content

5. Focused Neural Registries

5.1 How It Works Today

A page with is_neural_registry: true serves as a domain-wide context source. MCP tools can request /api/registry?domain=X and get all registry page content concatenated.

5.2 Group-Scoped Registries

When a group page has neural_registry: true in its HC metadata:

1. The group page's content (principle + child descriptions) becomes a focused registry
2. MCP requests for any child page automatically include the parent group's registry context
3. This is additive — domain-wide registries still work, group registries layer on top

MCP endpoint change:

GET /api/registry?domain=X&page=prds/vault

Response:
{
  "domain_registry": "...",           // existing domain-wide context
  "group_registry": "...",            // NEW: /prds/ group context
  "group_principle": "These PRDs...", // NEW: the group's "why"
  "siblings": [                       // NEW: other pages in the group
    { "slug": "teams", "title": "Teams PRD" },
    { "slug": "mcp", "title": "MCP PRD" }
  ]
}

5.3 Parent Chain Walk

For nested pages (domain/group/page/subpage), the MCP endpoint walks up the parent_page_id chain and collects registries at each level:

subpage → parent page → group page → domain
                                ↑ group registry
                         ↑ (no registry, skip)
  ↑ (the requested page)

This is a single recursive query, not multiple round trips:

WITH RECURSIVE ancestors AS (
  SELECT id, parent_page_id, html_content, page_name
  FROM pages WHERE id = $requested_page_id
  UNION ALL
  SELECT p.id, p.parent_page_id, p.html_content, p.page_name
  FROM pages p
  JOIN ancestors a ON p.id = a.parent_page_id
)
SELECT * FROM ancestors WHERE id != $requested_page_id;

6. Table View (List View Upgrade)

6.1 Replace PageManager.tsx

The current PageManager.tsx (168 lines) becomes PageDataTable.tsx. The view mode switcher in DashboardContent.tsx stays as-is — viewMode === 'list' renders the new component.

6.2 Table Columns

6.3 Search

Text input above the table. Filters on:

• page_name (case-insensitive contains)
• slug (case-insensitive contains)
• full_path (case-insensitive contains)

6.4 Sort State

const [sortColumn, setSortColumn] = useState<
  'name' | 'path' | 'folder' | 'status' | 'updated'
>('updated')
const [sortDirection, setSortDirection] = useState<
  'asc' | 'desc'
>('desc')

Click column header to sort. Click again to toggle direction. Active column header shows arrow indicator.

6.5 Hierarchy Indent

Pages with parent_page_id show indented in the table when sorted by name or path:

Vault PRD                      /prds/vault
  Vault Appendix               /prds/vault/appendix
Teams PRD                      /prds/teams
Rick Meekins                   /rick-meekins

6.6 Row Actions

6.7 Empty States

• No pages: "No pages yet. Create one with + Build Page or + New Page."
• Search with no results: "No pages match '{query}'. Clear search."

6.8 Responsive

Below 768px:

• Folder and Tags columns hidden
• Path column truncated with ellipsis
• Actions collapse to a single "..." menu

6.9 Component Interface

interface PageDataTableProps {
  pages: (Page & { domain?: Domain })[]
  domains: Domain[]
  onEditPage: (page: Page) => void
  onDeletePage: (pageId: string) => void
  onViewPage: (page: Page) => void
}

7. Dashboard UX for Hierarchy Management

7.1 "Create Group" Flow

Add a "Create Group" option to the + New Page / + Build Page area:

Clicking "+ Group" opens a minimal dialog:

This creates a page with:

• page_name = Group Name
• slug = the entered slug
• html_content = minimal HC metadata JSON only (no body HTML)
• hc_type = "group" in metadata
• group_principle = entered text (optional)
• neural_registry = checkbox value

7.2 "Add to Group" in Tree View

The existing tree view already supports drag-to-reparent. Add a context menu option:

Right-click page → "Move to Group..." → dropdown of existing group pages

7.3 "Add to Group" in Table View

In the table view, add a "Group" column option or inline action:

• Pages with no parent show "—" in the hierarchy column
• Clicking "—" opens a dropdown of available groups to assign to
• Pages already in a group show the group name as a link

7.4 Group Page Indicators

In all views (grid, table, tree):

7.5 Breadcrumb in Page Editor

When editing a page that's inside a group, show breadcrumb navigation:

domain.com / prds / vault
             ↑ clickable (goes to group page editor)

8. Reader Experience (Public-Facing)

8.1 Auto-Rendered Group Page

When a reader visits domain.com/prds/:

• MasteryMade design system (if domain has design profile, use it; otherwise default)
• Principle box at top (dark background, amber accents)
• Child pages listed with title, description, date
• Each child is a clickable link to its full URL
• If password-gated, gate displays before content
• Clean, fast, no JavaScript required (static HTML response)

8.2 Child Page Navigation

When a reader is on a child page (domain.com/prds/vault):

• The page renders as normal (custom HTML)
• If the group has other children, consider injecting a subtle navigation hint: previous/next links at bottom, "Part of: Platform PRDs" breadcrumb at top
• This is OPTIONAL and controlled by group metadata (show_nav: true)

8.3 Reader URL Experience

9. Implementation Sequence

10. What We're NOT Building

11. Success Criteria

• Group page at /prds/ auto-renders with principle box and child list when no custom HTML exists
• Table view shows all pages with sortable columns (name, path, folder, status, updated)
• Search filters pages by name/slug/path in real time
• "+ Group" button creates a group page with principle and optional registry flag
• Neural registry scoping returns group context when MCP requests a child page
• Three URL patterns all work: flat, grouped, nested (already working — just verify)
• No regressions in grid view, tree view, or existing page serving