Phase 9

Collaboration

A public operating layer for how ideas enter the studio, how changes are reviewed, and which creative experiments deserve implementation.

Public by defaultTraceable changes

Collaboration governance and creative direction

Small, memorable interactions with clear utility. No decorative complexity until content depth catches up.

Open structured issue Inspect component lab

Frame the change

Start from a route, component, document, or visible user problem instead of a vague preference.

GitHub issue, Feishu comment, or local doc note with context and goal.

Classify the surface

Decide whether the work belongs to product structure, content, interaction, visual system, or repository governance.

A clear owner area and a narrow first slice.

Ship with trace

Every meaningful phase should update source, tests, project map, progress log, version trace, GitHub, and Feishu.

Commit, deployment, verification record, and synced knowledge document.

Review creative debt

After each feature, inspect whether the site gained character or merely gained more UI.

Creative backlog update and a short expert review.

Issue templates

Public idea intake

Structured collaboration, feature ideas, and design discussion.

Route: /contact -> GitHub Issue Form
Evidence: .github/ISSUE_TEMPLATE/contact.yml

Project map

Project memory

Route map, stage records, version trace, and long-lived decisions.

Route: /knowledge + docs/
Evidence: docs/PROJECT_MAP.md

Component registry

Component proof

Reusable UI patterns, quality gates, and experiment inventory.

Route: /lab
Evidence: src/data/lab.ts

Feishu sync map

Cloud collaboration

Readable review surface, comments, and synced phase docs.

Route: Feishu Wiki
Evidence: docs/FEISHU_SYNC.md

Expert review

My direct read of the current homepage.

Do not add a mascot or heavy animation yet. First add interaction that feels like a programmer built a thoughtful studio: command traces, source-aware hover states, timeline scrubbing, and small inspectable details.

Strengths

The site already has a coherent warm developer-studio tone instead of a generic portfolio template.

Command Center, Knowledge, Uses, Lab, and Contact form a real operating system skeleton.

The interaction model is useful first: keyboard navigation, filters, copy feedback, lightbox, and player state.

The repo has unusually strong traceability for a personal homepage: docs, issues, deployment, and Feishu are linked.

Weaknesses

The site still needs one unmistakable signature interaction that people remember after leaving.

Some pages are structurally strong but emotionally thin because the content is still mostly seed material.

Projects need deeper case-study evidence: role, constraints, process, tradeoffs, outcome, and screenshots.

Music and photos are elegant, but they need richer personal metadata before they feel like a memory layer.

Creative backlog

Ideas worth testing, not blindly shipping.

NowInteraction

Command Trace

After a Command Center navigation, briefly show a subtle trace line such as `cmd.open('/lab')` near the destination header.

Why: It makes keyboard navigation feel authored and technical without pretending to be a terminal.
Risk: Can become noisy if it appears on every navigation; should be dismissive, brief, and reduced-motion aware.

NowUI

Source Hover

On Lab, Knowledge, and project cards, hover can reveal a tiny source path or reference token in a mono caption.

Why: It turns programmer identity into real inspectability rather than decorative code rain.
Risk: Long paths can overflow; must use stable truncation and mobile-safe disclosure.

NextInteraction

Reading Focus Lens

Refine the existing reader glow into a selectable paragraph focus mode with copy-link and outline sync.

Why: It adds craft to blog reading while serving real article navigation.
Risk: If over-animated, it will pollute the calm Claude-like reading tone.

NextContent

Memory Map

Connect posts, projects, photos, tools, and knowledge entries through a small related-object rail.

Why: The strongest future value is not more pages, but visible relationships between artifacts.
Risk: A full graph would be overkill; start as curated relations before any graph visualization.

NextComponent

Case Study Diff

Project pages can show before/after decisions as a visual diff: problem, constraint, tradeoff, shipped result.

Why: This would make portfolio pages feel like engineering thinking, not gallery summaries.
Risk: Needs real project evidence; otherwise it becomes a fake process widget.

LaterInteraction

Studio Companion

A tiny contextual helper that appears only in empty states or long pauses, never as a persistent pet.

Why: It could add playfulness, but only if it improves recovery, onboarding, or discovery.
Risk: High risk of looking juvenile. Defer until the core content and signature interactions are stronger.