-
mitrapclub_structural_identity_step1_solution_assessment.md
Please write Step 1 for the next change.
docs/plans/mitrapclub_structural_identity/mitrapclub_structural_identity_step1_solution_assessment.md Plans Plans and history
-
mitrapclub_structural_identity_step2_feature_description.md
The mitrapclub profile still carries three pieces of shared, not-club-specific config as-is: the generic forum nav (labels + the generic /tools/ operator page…
docs/plans/mitrapclub_structural_identity/mitrapclub_structural_identity_step2_feature_description.md Plans Plans and history
-
mitrapclub_structural_identity_step3_development_plan.md
Waiting for "Approved Step 3" before branching and starting Step 4.
docs/plans/mitrapclub_structural_identity/mitrapclub_structural_identity_step3_development_plan.md Plans Plans and history
-
mitrapclub_structural_identity_step4_implementation_summary.md
docs/plans/mitrapclub_structural_identity/mitrapclub_structural_identity_step4_implementation_summary.md Plans Plans and history
-
MIT Rap Club — de-genericize + extend checklist
Raw candidate list, not yet scoped or decided — input for the next FDP round
docs/plans/mitrapclub_theme_and_features_checklist.md Plans Plans and history
-
mit_rap_club_website_step1_solution_assessment.md
I would like to create a website for the MIT Rap Club.
docs/plans/mit_rap_club_website/mit_rap_club_website_step1_solution_assessment.md Plans Plans and history
-
mit_rap_club_website_step2_feature_description.md
MIT Rap Club has no online home; this app already supports branded community instances (chouse, qdb) but has no siteid, theme, or content configured for the cl…
docs/plans/mit_rap_club_website/mit_rap_club_website_step2_feature_description.md Plans Plans and history
-
mit_rap_club_website_step3_development_plan.md
Waiting for "Approved Step 3" before branching and starting Step 4.
docs/plans/mit_rap_club_website/mit_rap_club_website_step3_development_plan.md Plans Plans and history
-
mit_rap_club_website_step4_implementation_summary.md
docs/plans/mit_rap_club_website/mit_rap_club_website_step4_implementation_summary.md Plans Plans and history
-
Multi-Site Refactor Checklist
Use this checklist to refactor Zenmemes, Chouse, and QDB into explicit site components before adding another design.
docs/plans/multi_site_refactor_checklist.md Plans Plans and history
-
Multi-Site Refactor P0 — Step 1: Solution Assessment
Please write Step 1 of docs/fdp/FEATUREDEVELOPMENTPROCESS.md for P0 of docs/plans/multisiterefactorchecklist.md.
docs/plans/multi_site_refactor_p0/multi_site_refactor_p0_step1_solution_assessment.md Plans Plans and history
-
Multi-Site Refactor P0 — Step 2: Feature Description
Profile identity is only partly declared in SiteProfileRegistry; browser/offline identifiers and the profile-specific static-output rule are duplicated elsewhe…
docs/plans/multi_site_refactor_p0/multi_site_refactor_p0_step2_feature_description.md Plans Plans and history
-
Multi-Site Refactor P0 — Step 3: Development Plan
docs/plans/multi_site_refactor_p0/multi_site_refactor_p0_step3_development_plan.md Plans Plans and history
-
Multi-Site Refactor P0 — Step 4: Implementation Summary
docs/plans/multi_site_refactor_p0/multi_site_refactor_p0_step4_implementation_summary.md Plans Plans and history
-
Multi-Site Refactor P1 — Step 1: Solution Assessment
Please update the refactor checklist, merge into main, and prepare for P1.
docs/plans/multi_site_refactor_p1/multi_site_refactor_p1_step1_solution_assessment.md Plans Plans and history
-
Multi-Site Refactor P1 — Step 2: Feature Description
QDB's complete user experience is split through generic forum layers, so classic QDB behavior is difficult to evolve, isolate, and prove absent from the other…
docs/plans/multi_site_refactor_p1/multi_site_refactor_p1_step2_feature_description.md Plans Plans and history
-
Multi-Site Refactor P1 — Step 3: Development Plan
docs/plans/multi_site_refactor_p1/multi_site_refactor_p1_step3_development_plan.md Plans Plans and history
-
Multi-Site Refactor P1 — Step 4: Implementation Summary
docs/plans/multi_site_refactor_p1/multi_site_refactor_p1_step4_implementation_summary.md Plans Plans and history
-
Multi-Site Refactor P2 Browser and Offline Identity — Step 1: Solution Assessment
Oh, let's do that first then.
docs/plans/multi_site_refactor_p2_browser_offline_identity/multi_site_refactor_p2_browser_offline_identity_step1_solution_assessment.md Plans Plans and history
-
Multi-Site Refactor P2 Browser and Offline Identity — Step 2: Feature Description
Zenmemes-only browser and offline identifiers make profile switching unsafe on one origin and leave PWA identity ambiguous in published static artifacts.
docs/plans/multi_site_refactor_p2_browser_offline_identity/multi_site_refactor_p2_browser_offline_identity_step2_feature_description.md Plans Plans and history
-
Multi-Site Refactor P2 Browser and Offline Identity — Step 3: Development Plan
docs/plans/multi_site_refactor_p2_browser_offline_identity/multi_site_refactor_p2_browser_offline_identity_step3_development_plan.md Plans Plans and history
-
Multi-Site Refactor P2 Browser and Offline Identity — Step 4: Implementation Summary
docs/plans/multi_site_refactor_p2_browser_offline_identity/multi_site_refactor_p2_browser_offline_identity_step4_implementation_summary.md Plans Plans and history
-
Multi-Site Refactor P2 Presentation — Step 1: Solution Assessment
Never mind, it's a separate issue.
docs/plans/multi_site_refactor_p2_presentation/multi_site_refactor_p2_presentation_step1_solution_assessment.md Plans Plans and history
-
Multi-Site Refactor P2 Presentation — Step 2: Feature Description
Profile-specific presentation still relies on direct conditionals and embedded copy, making ordinary Zenmemes/Chouse variation and theme availability difficult…
docs/plans/multi_site_refactor_p2_presentation/multi_site_refactor_p2_presentation_step2_feature_description.md Plans Plans and history
-
Multi-Site Refactor P2 Presentation — Step 3: Development Plan
docs/plans/multi_site_refactor_p2_presentation/multi_site_refactor_p2_presentation_step3_development_plan.md Plans Plans and history
-
Multi-Site Refactor P2 Presentation — Step 4: Implementation Summary
docs/plans/multi_site_refactor_p2_presentation/multi_site_refactor_p2_presentation_step4_implementation_summary.md Plans Plans and history
-
Multi-Site Refactor P3 — Step 1: Solution Assessment
Please write Step 1 of docs/fdp/FEATUREDEVELOPMENTPROCESS.md for P3, taking into account that I'll continue it from a new conversation, and it needs to update…
docs/plans/multi_site_refactor_p3/multi_site_refactor_p3_step1_solution_assessment.md Plans Plans and history
-
Multi-Site Refactor P3 — Step 2: Feature Description
The declarative multi-site contract is covered by tests that still encode site names and partial expectations, so a contract change or fourth profile can regre…
docs/plans/multi_site_refactor_p3/multi_site_refactor_p3_step2_feature_description.md Plans Plans and history
-
Multi-Site Refactor P3 — Step 3: Development Plan
docs/plans/multi_site_refactor_p3/multi_site_refactor_p3_step3_development_plan.md Plans Plans and history
-
Multi-Site Refactor P3 — Step 4: Implementation Summary
docs/plans/multi_site_refactor_p3/multi_site_refactor_p3_step4_implementation_summary.md Plans Plans and history
-
Multi-Site Refactor Review — Step 1: Solution Assessment
We have now developed 3 different site designs and configs with this framework: zenmemes, qdb, and chouse.
docs/plans/multi_site_refactor_review/multi_site_refactor_review_step1_solution_assessment.md Plans Plans and history
-
Multi-Site Refactor Review — Step 2: Feature Description
Site-specific behavior for Zenmemes, Chouse, and QDB is implemented through a mix of profile fields, direct name checks, specialized templates, and fixed brows…
docs/plans/multi_site_refactor_review/multi_site_refactor_review_step2_feature_description.md Plans Plans and history
-
Multi-Site Refactor Review — Step 3: Development Plan
docs/plans/multi_site_refactor_review/multi_site_refactor_review_step3_development_plan.md Plans Plans and history
-
Multi-Site Refactor Review — Step 4: Documentation Summary
docs/plans/multi_site_refactor_review/multi_site_refactor_review_step4_implementation_summary.md Plans Plans and history
-
Music media embeds — Railspike debug log
Debug mode: enabled (new workflow; project-root .railspikedebugon file present).
docs/plans/music_media_embeds/music_media_embeds_debug_log.md Plans Plans and history
-
Music embed feasibility and acceptance boundaries
Planning evidence gathered October 15, 2026; no application implementation or audio-playback acceptance is claimed.
docs/plans/music_media_embeds/music_media_embeds_feasibility_notes.md Plans Plans and history
-
music_media_embeds_step1_solution_assessment.md
Let us continue with docs/plans/mediaembedsupportchecklist.md.
docs/plans/music_media_embeds/music_media_embeds_step1_solution_assessment.md Plans Plans and history
-
music_media_embeds_step2_feature_description.md
SoundCloud and Bandcamp links lack the in-thread listening experience already available for Spotify.
docs/plans/music_media_embeds/music_media_embeds_step2_feature_description.md Plans Plans and history
-
music_media_embeds_step3_development_plan.md
Status: Steps 1–2 approved; Step 3 drafted for review.
docs/plans/music_media_embeds/music_media_embeds_step3_development_plan.md Plans Plans and history
-
music_media_embeds_step4_implementation_summary.md
Branch: feature/music-media-embeds.
docs/plans/music_media_embeds/music_media_embeds_step4_implementation_summary.md Plans Plans and history