sdarbinyan/marketplaces
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
2d8d6b6dc4656a26a3d454c60fd8f117f54d075b
marketplaces/docs/SPRINT-PLAN.md
sdarbinyan 2d8d6b6dc4 feat(admin): order management 
Sprint 23.

New features/admin/orders/ module, same container/facade/service split as
admin/products and admin/categories.

- AdminOrder model + AdminOrdersLocalGateway seeding 24 deterministic
  synthetic orders (no real order data source exists anywhere in this
  repo - explicitly a placeholder, not a mock of production volume)
- list: search, status filter, pagination, CSV export (client-side Blob
  download)
- detail: customer/payment/shipping, itemized total, status timeline,
  change-status dropdown, refund request + cancel (window.confirm-gated),
  separate customer-facing vs internal notes, print invoice via
  window.print() with @media print hiding non-invoice chrome
- wired into /:lang/backoffice/orders(/:id), replacing the coming-soon
  placeholder

docs/ADMIN.md + docs/BACKEND.md updated; dashboard's Orders/Revenue cards
(Sprint 19) remain intentionally un-wired to this mock and still render
pending-backend.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-15 10:50:59 +04:00

7.1 KiB
Raw Blame History

Sprint Plan (working doc, delete after release)

Repo already past old "Sprint 19" (dashboard). Renumbering user's Sprint7+ roadmap to continue actual sequence: Sprint 20 = old "Sprint 7" (Categories) ... Sprint 30 = old "Sprint 17" (Final Release).

Pattern to follow (mirrors admin/products): models/, services/<x>-gateway.interface.ts + <x>-local.gateway.ts (IndexedDB via existing local-storage service), facade/, pages/, components/. Local-only until backend endpoint exists — log gap in docs/BACKEND.md.

Autonomy: no stop-and-ask except missing API contract / business decision / secrets / external config / legal / multi-valid-design-fork. Commit after each sprint, conventional commits, no push. Quality gate before marking sprint done: build, typecheck, lint (if configured), responsive check, a11y pass, docs updated, no dead code, arch:check green.

Notify user: from Sprint 20 (Categories) once product↔category link + admin categories CRUD exist, catalog can start receiving real items (currently admin-products already has categoryId field but no category source of truth — that's the point where "adding items to catalog" becomes real, not mocked dropdown).

Sprint 20 — Category Management ✅ done

  • AdminCategory model (id, parentId, title, translations, slug, icon, image, seo, visible, order, draft/published status, soft-delete)
  • AdminCategoriesGateway interface + local (in-memory, seeded from BackofficeDataService) gateway, mirrors products gateway
  • AdminCategoriesFacade (signals, CRUD, tree ops, slug validation, draft recovery)
  • Categories list page: indented tree, native HTML5 DnD reorder, visibility toggle, item counter, empty state, include-deleted filter + restore
  • Category editor: name/slug (+ uniqueness validation), translations editor, icon field, image via MediaPickerComponent, SEO fields, breadcrumb preview
  • Delete validation (blocked if has children or itemsCount>0) + soft-delete/restore
  • Draft/publish workflow + localStorage draft recovery (mirrors Project Editor autosave) + unsaved-changes CanDeactivate guard (mirrors projectEditorDirtyGuard)
  • Wired into admin routing (app.routes.ts, replaced coming-soon placeholder)
  • Updated docs/ADMIN.md (new Sprint 20 section), docs/BACKEND.md (categories gap rewritten with real field list)
  • [~] Responsive/a11y: reuses existing FormField/Input/Table/Button/EmptyState a11y wiring; live-browser click-through blocked by safety classifier on the guarded admin route (see below) — verified via tsc/build/arch:check only
  • Commit: feat(admin): complete category management
  • Note: admin/products' category dropdown still uses its own AdminProductsGateway.loadCategories(), not this new gateway — unification deferred to Sprint 21 (documented in BACKEND.md).

Sprint 21 — Product Management completion ✅ done

  • Audit + add missing: archived (soft, list filter + archive/restore action), barcode, variants (lightweight name|price|quantity), relatedProductIds (checkbox picker)
  • Wired products to real AdminCategoriesGateway (AdminProductsLocalGateway now seeds from AdminCategoriesLocalGateway, replacing its own BackofficeDataService category seed)
  • Gallery via MediaPickerComponent (add/remove thumbnails); translation editor already existed (Sprint pre-19); preview (computed discounted price); infinite-scroll toggle on list (facade.loadMore() appends vs pagination)
  • Updated docs/ADMIN.md (new Sprint 21 section), docs/BACKEND.md (item 6 rewritten with real field list)
  • Commit: feat(admin): complete product management
  • Known trade-off: related-products picker sources from whatever page is currently loaded in AdminProductsFacade.products(), not a full catalog search — documented in ADMIN.md, fine at current mock scale.

Sprint 22 — Media System hardening ✅ done

  • Folder support (flat, filter-based), tags (edit + filter), search (already existed)
  • Resize/compression on upload (canvas downscale + re-encode, raster only) + SVG script-sanitization + file-type/size validation with real surfaced errors
  • Confirmed reuse: category images (20), product gallery (21), branding logo/compact-logo/favicon (22, newly wired). Static pages: no image fields (not a gap). Hero: no dedicated field exists.
  • Storage abstraction documented (MediaRepository abstract class was already the abstraction)
  • Commit: feat(media): reusable media management
  • Scoped down from ticket: no interactive crop UI (compression/resize only); folders are a flat tag, not a real folder entity/hierarchy.

Sprint 23 — Orders (mock/local, flag backend gap) ✅ done

  • AdminOrder model + local gateway (24 seeded synthetic orders, no real data source existed)
  • List: search, status filter, pagination, CSV export
  • Detail: customer/payment/shipping, itemized total, status timeline, change-status, refund request + cancel (confirm-gated), customer notes + internal notes, print invoice (window.print + @media print)
  • docs/ADMIN.md (new Sprint 23 section), docs/BACKEND.md item 7 rewritten
  • Commit: feat(admin): order management

Sprint 24 — Transactions (mock/local)

  • Payments/refunds/QR list, status, history, export, filters, search, retry, fraud flags, audit log view
  • Commit: feat(admin): transaction management

Sprint 25 — Users & Roles

  • Users/roles/permissions models (local), marketplace vs office admin distinction
  • Invitations, passwordless login (reuse existing Telegram QR pattern), session/device manager, audit trail
  • Commit: feat(admin): users and permissions

Sprint 26 — Monitoring

  • Audit/security/login logs views (local), API/error/warning feed, queue/webhook placeholders, health page
  • Commit: feat(admin): monitoring center

Sprint 27 — Analytics

  • Dashboard extensions: sales/revenue/orders/visitors/products/categories charts, date ranges, export
  • Commit: feat(admin): analytics dashboard

Sprint 28 — Marketplace Polish

  • Lighthouse + a11y sweep, animations, skeletons/empty/error states, responsive fixes, SEO/meta/social preview/robots/sitemap
  • Commit: refactor: marketplace release polish

Sprint 29 — Release Candidate

  • Dead code cleanup, remove TODOs/console logs/debug code, optimize imports/bundle/images/CSS, translation validation, build/type/lint validation, doc validation, arch review, CHANGELOG + release notes
  • Commit: chore: release candidate

Sprint 30 — Final Release

  • Full verify pass (build, routing, responsive, translations, admin, marketplace, editor, media, login, bootstrap, APIs, security assumptions), final report
  • Then (only after explicit go-ahead, push is a confirm-required action): git push

Stop conditions (ask user)

  • Real backend API contract needed (orders/transactions/users are local-mock by design per above — flagged, not blocking)
  • Ambiguous business rule (e.g. category deletion policy specifics) not inferable from existing product-deletion pattern
  • Credentials/external service config
  • Legal/product-only decision
  • Two equally valid architectures for same feature
Reference in New Issue View Git Blame Copy Permalink