admin/docs - docs - Gitea: Git with a cup of tea

admin/docs

Fork 0

Commit Graph

Author	SHA1	Message	Date
masoodafar-web	01244f426e	docs: package-based transformation — complete roadmap + UX impact + feature backlog New documents: - roadmap/FEATURE-BACKLOG.md: 12 kept RPCs → feature tasks with priority, target pages, and time estimates (F1-F12) - roadmap/PACKAGE-TRANSFORMATION-UX.md: UX impact analysis — before/after wireframes for 19 pages (10 FO + 9 BO), customer + admin experience changes, future needs prediction - roadmap/PACKAGE-TRANSFORMATION-TASKS.md: step-by-step implementation plan (6 phases, ~13 day critical path), atomic tasks with code diffs, dependency graph, test checklist Updated: - cms/GRPC-SERVICES-AUDIT.md: cross-references to new docs Total: 998 lines of documentation covering: - 12 RPC feature tasks prioritized by package-based relevance - 19 page wireframes (before/after comparison) - 39 transformation tasks broken into 6 phases - 10 predicted future requirements (N1-N10) - Risk analysis + rollback plan + calendar	2026-02-24 23:18:50 +03:30
masoodafar-web	3575e483b9	docs: deep analysis of 24 dead gRPC RPCs — keep 12, archive 12 Analyzed all 24 dead RPC implementations line-by-line: - 12 KEEP (future-proof): CustomerReorderPreviousOrder, CustomerTrackOrder, CalculateOrderPV, GetInventorySummary, GetStockValueReport, BulkAddStock, BulkUpdateProductStock, GetConfigurationByKey, UpdateCustomerSettings, ChangeNetworkParent, AssignFeatureToMembership, GetLowStockProducts - 12 ARCHIVE: fms.proto (2), BulkAdjustStock, 2 empty order stubs, 2 non-functional configs, 2 redundant city ops, 3 duplicate RPCs Key findings: - 17/24 were actually FULLY IMPLEMENTED, just never wired to frontend - fms.proto is the only completely dead proto file (no service class) - Archive != Delete — marked for exclusion only	2026-02-24 22:40:44 +03:30
masoodafar-web	09b8b804d4	docs: audit all CMS gRPC services — 342 RPCs, 125 unused from frontends, 24 dead code	2026-02-24 22:25:53 +03:30

Author

SHA1

Message

Date

masoodafar-web

01244f426e

docs: package-based transformation — complete roadmap + UX impact + feature backlog

New documents:
- roadmap/FEATURE-BACKLOG.md: 12 kept RPCs → feature tasks with priority,
  target pages, and time estimates (F1-F12)
- roadmap/PACKAGE-TRANSFORMATION-UX.md: UX impact analysis —
  before/after wireframes for 19 pages (10 FO + 9 BO),
  customer + admin experience changes, future needs prediction
- roadmap/PACKAGE-TRANSFORMATION-TASKS.md: step-by-step implementation
  plan (6 phases, ~13 day critical path), atomic tasks with
  code diffs, dependency graph, test checklist

Updated:
- cms/GRPC-SERVICES-AUDIT.md: cross-references to new docs

Total: 998 lines of documentation covering:
- 12 RPC feature tasks prioritized by package-based relevance
- 19 page wireframes (before/after comparison)
- 39 transformation tasks broken into 6 phases
- 10 predicted future requirements (N1-N10)
- Risk analysis + rollback plan + calendar

2026-02-24 23:18:50 +03:30

masoodafar-web

3575e483b9

docs: deep analysis of 24 dead gRPC RPCs — keep 12, archive 12

Analyzed all 24 dead RPC implementations line-by-line:
- 12 KEEP (future-proof): CustomerReorderPreviousOrder, CustomerTrackOrder,
  CalculateOrderPV, GetInventorySummary, GetStockValueReport, BulkAddStock,
  BulkUpdateProductStock, GetConfigurationByKey, UpdateCustomerSettings,
  ChangeNetworkParent, AssignFeatureToMembership, GetLowStockProducts
- 12 ARCHIVE: fms.proto (2), BulkAdjustStock, 2 empty order stubs,
  2 non-functional configs, 2 redundant city ops, 3 duplicate RPCs

Key findings:
- 17/24 were actually FULLY IMPLEMENTED, just never wired to frontend
- fms.proto is the only completely dead proto file (no service class)
- Archive != Delete — marked for exclusion only

2026-02-24 22:40:44 +03:30

masoodafar-web

09b8b804d4

docs: audit all CMS gRPC services — 342 RPCs, 125 unused from frontends, 24 dead code

2026-02-24 22:25:53 +03:30

3 Commits