From 993aab906bf329a56f91274eb7d4af95274ec649 Mon Sep 17 00:00:00 2001 From: yusyus Date: Sun, 30 Nov 2025 20:18:08 +0300 Subject: [PATCH] docs: Update A1 task descriptions with new design - A1.3: Change from web form to MCP submit_config tool - A1.4: Change from rating system to static website catalog - A1.5: Change from search/filter to rating/voting system - A1.6: Clarify GitHub Issues-based review approach All changes aligned with approved plan for website as read-only catalog, MCP as active manager architecture. --- FLEXIBLE_ROADMAP.md | 26 +++++++++++++++++++++----- 1 file changed, 21 insertions(+), 5 deletions(-) diff --git a/FLEXIBLE_ROADMAP.md b/FLEXIBLE_ROADMAP.md index 8100e45..3c888b2 100644 --- a/FLEXIBLE_ROADMAP.md +++ b/FLEXIBLE_ROADMAP.md @@ -38,12 +38,28 @@ Small tasks that build community features incrementally - **Features:** List 24 configs, filter by category, download by name, save to local directory - **Commands:** `list_available=true`, `category='web-frameworks'`, `config_name='react'` - **Branch:** `feature/a1-config-sharing` -- [ ] **Task A1.3:** Create basic config upload form (HTML + backend) -- [ ] **Task A1.4:** Add config rating/voting system -- [ ] **Task A1.5:** Add config search/filter functionality -- [ ] **Task A1.6:** Add user-submitted config review queue +- [ ] **Task A1.3:** Add MCP tool `submit_config` to submit custom configs (Issue #11) + - **Purpose:** Allow users to submit custom configs via MCP (creates GitHub issue) + - **Features:** Validate config JSON, create GitHub issue, auto-label, return issue URL + - **Approach:** GitHub Issues backend (safe, uses GitHub auth/spam detection) + - **Time:** 2-3 hours +- [ ] **Task A1.4:** Create static config catalog website (GitHub Pages) (Issue #12) + - **Purpose:** Read-only catalog to browse/search configs (like npm registry) + - **Features:** Static HTML/JS, pulls from API, search/filter, copy JSON button + - **Architecture:** Website = browse, MCP = download/submit/manage + - **Time:** 2-3 hours +- [ ] **Task A1.5:** Add config rating/voting system (Issue #13) + - **Purpose:** Community feedback on config quality + - **Features:** Star ratings, vote counts, sort by rating, "most popular" section + - **Options:** GitHub reactions, backend database, or localStorage + - **Time:** 3-4 hours +- [ ] **Task A1.6:** Admin review queue for submitted configs (Issue #14) + - **Purpose:** Review community-submitted configs before publishing + - **Approach:** Use GitHub Issues with labels (no custom code needed) + - **Workflow:** Review → Validate → Test → Approve/Reject + - **Time:** 1-2 hours (GitHub Issues) or 4-6 hours (custom dashboard) -**Start Small:** ~~Pick A1.1 first (simple JSON endpoint)~~ ✅ A1.1 Complete! ~~Pick A1.2 next (MCP tool)~~ ✅ A1.2 Complete! Pick A1.3 next (upload form) +**Start Small:** ~~Pick A1.1 first (simple JSON endpoint)~~ ✅ A1.1 Complete! ~~Pick A1.2 next (MCP tool)~~ ✅ A1.2 Complete! Pick A1.3 next (MCP submit tool) #### A2: Knowledge Sharing (Website Feature) - [ ] **Task A2.1:** Design knowledge database schema