zenmemes

New post

zenmemes Platform Docs

Docs home

Documents

2,619 documents

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  16. nav_active_theme_override — Railspike debug log

    Debug mode resolved from the project marker .railspikedebugon (new workflow, no explicit request).

    docs/plans/nav_active_theme_override/nav_active_theme_override_debug_log.md Plans Plans and history

  17. nav_active_theme_override_step1_solution_assessment.md

    We seem to have experienced a regression in the Word 97 and Midnight themes.

    docs/plans/nav_active_theme_override/nav_active_theme_override_step1_solution_assessment.md Plans Plans and history

  18. nav_active_theme_override_step2_feature_description.md

    On a normal page load, the selected nav button in Word 97 and Midnight shows the shared dark-blue active style instead of the theme's sunken gray.

    docs/plans/nav_active_theme_override/nav_active_theme_override_step2_feature_description.md Plans Plans and history

  19. nav_active_theme_override_step3_development_plan.md

    docs/plans/nav_active_theme_override/nav_active_theme_override_step3_development_plan.md Plans Plans and history

  20. nav_active_theme_override_step4_implementation_summary.md

    Branch: fix/nav-active-theme-override · Planning commit: 4e67e5f3

    docs/plans/nav_active_theme_override/nav_active_theme_override_step4_implementation_summary.md Plans Plans and history

  21. Debug log — nav_links_load_stability

    docs/plans/nav_links_load_stability/nav_links_load_stability_debug_log.md Plans Plans and history

  22. Step 1: Solution Assessment — Stable Messages/Invite Nav Buttons

    As a user, noticed that the Messages and Invite nav buttons don't appear right on page load, but get added to the page after load, which feels janky.

    docs/plans/nav_links_load_stability/nav_links_load_stability_step1_solution_assessment.md Plans Plans and history

  23. Step 2: Feature Description — Stable Messages/Invite Nav Buttons (Revised)

    Stage 1 found no script that inserts the nav buttons after load.

    docs/plans/nav_links_load_stability/nav_links_load_stability_step2_feature_description.md Plans Plans and history

  24. Step 3: Development Plan — Stable Messages/Invite Nav Buttons (Revised)

    docs/plans/nav_links_load_stability/nav_links_load_stability_step3_development_plan.md Plans Plans and history

  25. Step 4: Implementation Summary — Stable Messages/Invite Nav Buttons

    docs/plans/nav_links_load_stability/nav_links_load_stability_step4_implementation_summary.md Plans Plans and history

  26. Negative Score Liked Listing Filter Plan V1

    Threads whose root post has postscoretotal < 0 should not appear on the Liked board listing pages.

    docs/plans/negative_score_listing_filter_plan_v1.md Plans Plans and history

  27. New Thread Board Stall Investigation

    After creating a new thread, the created thread page renders successfully, but subsequent board requests appear unresponsive for roughly 5-15 seconds.

    docs/plans/new_thread_board_stall_investigation_v1.md Plans Plans and history

  28. No-JavaScript basic access — Railspike debug log

    No supported findings.

    docs/plans/nojs_basic_access_debug_log.md Plans Plans and history

  29. nojs_basic_access_step1_solution_assessment.md

    As a user with JavaScript disabled, I want to have access to basic features of the site.

    docs/plans/nojs_basic_access_step1_solution_assessment.md Plans Plans and history

  30. nojs_basic_access_step2_feature_description.md

    Visitors with JavaScript disabled need to browse and contribute basic text content through the ordinary site interface.

    docs/plans/nojs_basic_access_step2_feature_description.md Plans Plans and history

  31. nojs_basic_access_step3_development_plan.md

    Zenmemes public forum: ordinary entry → pagination → reading → anonymous thread/reply → persisted content after reload, including retained-draft validation rec…

    docs/plans/nojs_basic_access_step3_development_plan.md Plans Plans and history

  32. Offline Board Navigation Step 1 Solution Assessment

    Allow every read-only Board filter/sort view and Tags index/result view to work

    docs/plans/offline_board_navigation/offline_board_navigation_step1_solution_assessment.md Plans Plans and history

  33. Offline Board Navigation Step 2 Feature Description

    Offline normal navigation currently supports saved threads and Board state at

    docs/plans/offline_board_navigation/offline_board_navigation_step2_feature_description.md Plans Plans and history

  34. Offline Board Navigation Step 3 Development Plan

    docs/plans/offline_board_navigation/offline_board_navigation_step3_development_plan.md Plans Plans and history

  35. Offline Board Navigation Step 4 Implementation Summary

    docs/plans/offline_board_navigation/offline_board_navigation_step4_implementation_summary.md Plans Plans and history

  36. Offline Indicator Compaction Step 2 Feature Description

    The archive timestamp and reader revision currently appear as a full sentence

    docs/plans/offline_indicator_compaction/offline_indicator_compaction_step2_feature_description.md Plans Plans and history

  37. Offline Indicator Compaction Step 3 Development Plan

    docs/plans/offline_indicator_compaction/offline_indicator_compaction_step3_development_plan.md Plans Plans and history

  38. Offline Indicator Compaction Step 4 Implementation Summary

    docs/plans/offline_indicator_compaction/offline_indicator_compaction_step4_implementation_summary.md Plans Plans and history

  39. Offline Indicator Corner Links Step 1 Solution Assessment

    Redesign the offline mode indicator to not take up extra vertical space (probably top corner?).

    docs/plans/offline_indicator_corner_links/offline_indicator_corner_links_step1_solution_assessment.md Plans Plans and history

  40. Offline Indicator Corner Links Step 2 Feature Description

    The offline-mode bar takes a full row above reader content and links only to Outbox.

    docs/plans/offline_indicator_corner_links/offline_indicator_corner_links_step2_feature_description.md Plans Plans and history