Clarify reader implementation plan data flow and SSR responsibilities

Browse Source

- Update Section 1.4 with detailed data flow diagram showing SSR skeleton approach
- Add Section 1.5 documenting SSR vs Client-Side responsibilities
- Clarify that SSR provides HTML shell with initial data, TypeScript handles UI
- Document specific examples of what SSR renders vs what TypeScript manages
- Remove confusing 'embedded JSON' terminology for clearer hybrid approach

These changes make the implementation plan more precise and implementation-ready
by clearly separating SSR (Go template) from client-side (TypeScript) concerns.

...

This commit is contained in:

john-okeefe

2026-04-03 22:29:05 -04:00

parent e7ce0cbe94

commit fa2d4c0fd8

1 changed files with 377 additions and 825 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

READER_IMPLEMENTATION_PLAN.md

+377 -825

File diff suppressed because it is too large Load Diff