Skip to content

RFC: featured content requirements and layout#4

Open
danielnaab wants to merge 6 commits intomainfrom
worktree-featured-content-design
Open

RFC: featured content requirements and layout#4
danielnaab wants to merge 6 commits intomainfrom
worktree-featured-content-design

Conversation

@danielnaab
Copy link
Copy Markdown
Member

Summary

  • Adds docs/featured-content.md analyzing how to present Forms, Messaging (Notify), Document Extractor, and Forms Lab as featured projects
  • Evaluates the data model gap (3 of 4 repos not yet in repos.json), proposes 4 options ranked by complexity
  • Compares layout approaches for home page (enhanced card vs. hero spotlight vs. unchanged) and work index (section heading vs. pinned section vs. visual-only emphasis)
  • Recommends: enhanced FeaturedCard on the home page grid + section heading in the work index that preserves "same collection" filtering behavior
  • Identifies open questions (repo public status, Forms Lab positioning, highlights field authoring)

Intent

This is a design document for discussion, not an implementation PR. Seeking alignment on:

  1. Data strategy — do we ship before repos go public (approach D: manual entries) or wait (approach A)?
  2. Layout direction — enhanced card in the grid, or something more dramatic?
  3. Forms Lab positioning — companion, docs site, or independent product?

Test plan

  • Review the trade-off analysis in docs/featured-content.md
  • Decide on open questions before implementation begins

Analyzes the data model gap (repos not yet in snapshot), evaluates
layout options for the home page and work index, and proposes an
implementation sequence for highlighting Forms, Messaging, Document
Extractor, and Forms Lab.
@danielnaab danielnaab temporarily deployed to preview/worktree-featured-content-design April 28, 2026 21:47 — with GitHub Actions Inactive
forms-lab is now public, forms is pending, flexion-notify coming soon.
Approach A (wait for refresh) confirmed. Note the messaging.md →
flexion-notify.md rename needed.
@danielnaab danielnaab temporarily deployed to preview/worktree-featured-content-design April 28, 2026 22:01 — with GitHub Actions Inactive
Both are standalone featured items. Cross-linked via `related` field
on detail pages and placed adjacent in the home grid. Promote related
field from stretch to main implementation sequence.
@danielnaab danielnaab temporarily deployed to preview/worktree-featured-content-design April 28, 2026 22:04 — with GitHub Actions Inactive
- Rename messaging.md → flexion-notify.md to match repo name
- Create forms-lab.md overlay content
- Add highlights and related fields to overlay front-matter
- Extend Overlay type and parser to support highlights/related
- Mark forms, forms-lab, document-extractor, flexion-notify as featured
- Build FeaturedCard component with title, summary, highlights, and CTA
- Wire FeaturedCard into home page with intentional ordering
  (Forms and Forms Lab adjacent)
- Adjust featured grid: 2 cols at medium, 4 cols at wide
- Add "Featured" / "All projects" section headings to work index
- Implement related projects cross-links on detail pages
  (Forms ↔ Forms Lab)
- Update work-detail tests for new catalog prop
@danielnaab danielnaab temporarily deployed to preview/worktree-featured-content-design April 28, 2026 22:47 — with GitHub Actions Inactive
The overlay body was stored as raw markdown but rendered via raw() on
detail pages, which expects HTML. Now uses marked.parse() during load
so headings, emphasis, and paragraphs render correctly.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant