zenmemes

New post

zenmemes Platform Docs

Docs home

Documents

2,229 documents

Filters
  1. 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

  2. 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

  3. 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

  4. 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

  5. mobile_compose_keyboard_step1_solution_assessment.md

    Source-Thread: thread-20261031051903-0e8e7df4

    docs/plans/mobile_compose_keyboard/mobile_compose_keyboard_step1_solution_assessment.md Plans Plans and history

  6. mobile_compose_keyboard_step2_feature_description.md

    Source-Thread: thread-20261031051903-0e8e7df4

    docs/plans/mobile_compose_keyboard/mobile_compose_keyboard_step2_feature_description.md Plans Plans and history

  7. mobile_compose_keyboard_step3_development_plan.md

    Source-Thread: thread-20261031051903-0e8e7df4

    docs/plans/mobile_compose_keyboard/mobile_compose_keyboard_step3_development_plan.md Plans Plans and history

  8. mobile_compose_keyboard_step4_implementation_summary.md

    Effort study: v3/mobilecomposekeyboard · ledger (standing P2 enrollment)

    docs/plans/mobile_compose_keyboard/mobile_compose_keyboard_step4_implementation_summary.md Plans Plans and history

  9. Multi-redemption invites — Railspike debug log

    Source: docs/railspike/docs/workflow/step1solutionassessment.md, options and review gate.

    docs/plans/multi_redemption_invites/multi_redemption_invites_debug_log.md Plans Plans and history

  10. Superseded scope v1 — multi-redemption invites

    Historical record: superseded by the user’s backend-only direction on 2026-10-31 UTC.

    docs/plans/multi_redemption_invites/multi_redemption_invites_scope_v1_history.md Plans Plans and history

  11. multi_redemption_invites_step1_solution_assessment.md

    Effort study: railspike-effort / v3/multiredemptioninvites; P2 ledger

    docs/plans/multi_redemption_invites/multi_redemption_invites_step1_solution_assessment.md Plans Plans and history

  12. multi_redemption_invites_step2_feature_description.md

    Effort study: railspike-effort / v3/multiredemptioninvites; P2 ledger

    docs/plans/multi_redemption_invites/multi_redemption_invites_step2_feature_description.md Plans Plans and history

  13. multi_redemption_invites_step3_development_plan.md

    Effort study: railspike-effort / v3/multiredemptioninvites; ledger

    docs/plans/multi_redemption_invites/multi_redemption_invites_step3_development_plan.md Plans Plans and history

  14. multi_redemption_invites_step4_implementation_summary.md

    Effort study: railspike-effort / v3/multiredemptioninvites; ledger

    docs/plans/multi_redemption_invites/multi_redemption_invites_step4_implementation_summary.md Plans Plans and history

  15. 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

  16. 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

  17. 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

  18. 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

  19. 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

  20. 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

  21. 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

  22. 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

  23. 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

  24. 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

  25. 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

  26. 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

  27. 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

  28. 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

  29. 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

  30. 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

  31. 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

  32. 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

  33. 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

  34. 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

  35. 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

  36. 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

  37. 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

  38. 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

  39. 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

  40. 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