tegwick
0aeec59fd7
Assistant: codex Assistant-Model: gpt-6.1-sol Assistant-Session: 01a10e2d-a5ef-7e92-b03d-b1694e915680
3.2 KiB
| id | type | title | domain | repo | status | owner | topic_slug | created | updated | state_hub_workstream_id |
|---|---|---|---|---|---|---|---|---|---|---|
| CSOC-WP-0011 | workplan | Establish UI framework architecture before broad Bubble UX rebuild | communication | coulomb-social | backlog | codex | coulomb-social | 2026-10-06 | 2026-10-06 | b83ec7e8-9820-5b53-965a-32ad34c11ee3 |
User milestone and priority
After the first content transfer, the interface has a consistent foundation for finding spaces, opening pages ordered by latest changes, editing/copying protocols and distributing notes by clipboard. New Bubble use cases can reuse the same navigation, forms, interaction and permission patterns. The framework decision is explicit and reviewed before broad UX investment; no new frontend stack is assumed merely to make the current migration work.
User steering on 2026-10-06: prioritize content migration, then establish framework architecture before rebuilding many UI elements. CSOC-WP-0008-T02/T03/T09 remain first; this backlog workplan does not block source capture or the first transfer.
Inventory existing UI and observed Bubble interaction patterns
id: CSOC-WP-0011-T01
status: todo
priority: medium
state_hub_task_id: "1a6b9136-19b2-58c6-afae-5670f12314c6"
Review current Django templates, routes, forms, permission checks and clipboard JavaScript together with user-reviewed Bubble journeys. Describe navigation, latest-change ordering, protocol copying and editing, reusable components and accessibility needs. Use captured UI evidence separately from private content.
Decide the UI framework boundaries and extension contract
id: CSOC-WP-0011-T02
status: todo
priority: medium
state_hub_task_id: "73765a5b-ea06-5aa3-9c9c-4b24d23d5f24"
Prepare an ADR comparing the existing server-rendered foundation with progressive interaction or a distinct frontend only where user needs justify it. Specify component ownership, routing/state, server validation, auth/permission boundary, asset delivery and regression test contract. Review with the user before broad UX implementation. Avoid coupling the content migration format to the UI stack.
Demonstrate the foundation on the accepted ReichelAg journey
id: CSOC-WP-0011-T03
status: todo
priority: medium
state_hub_task_id: "8ebc4a82-0444-52b6-88bb-e448d9904006"
After content acceptance and framework review, implement one representative space/page interaction on the decided foundation. Keep the full-protocol copy, independent edit, latest-protocol discovery and native clipboard workflows under established regression coverage. User reviews consistency and usability before other Bubble UI surfaces are rebuilt. Register later UI gaps as live follow-ups.
Founder content-first decision: e67cfd2e-e55d-4b42-947a-b279b6287c55.
Concrete source journey confirmed: Spaces -> ReichelAg -> Pages, ordered by latest changes. First cohort imported; source creation/modification timestamps preserved in markdown. Current app navigation is index-first/alphabetical. Architecture/representative proof must define source timestamps versus local edit times and implement latest-change discovery without losing provenance. Visual assets are preserved in content storage; accepted cover/image delivery is still CSOC-WP-0008-T05 rather than an assumed UI capability.