24-06-2026
SourceOne — Detailed Page Module
Public detailed product page, RFQ flow, admin CMS, and 2,500+ product content programme
| Field | Value |
| Document Title | SourceOne Detailed Page Module – Requirements Document |
| Version | 1.0 (Draft) |
| Date | 2026-06-11 |
| Author | Prashant Y. |
| Owner / Product | Clyzo Platform Team |
| Reviewers | Tech Lead, Design Lead, QA Lead, Product Owner, SourceOne Integration Owner, Content Lead, SEO Lead |
| Status | For Review |
| Related Module | Product Module Management (Module 4) — see Section 1.2 for boundary |
This module has two parallel critical paths: an engineering programme of ~5–6 weeks, and a content programme that the source brief describes as 'more than months'.
Treat them as separate tracks with separate owners.
| # | Phase | Effort | Primary Output |
| 1 | Module Requirements Document | 1 day | This document, signed off |
| 2 | UI / UX | 4–5 days | Detailed page design, RFQ popup design |
| 3 | Frontend Development | 4–6 days | Public detailed page, admin detailed info page |
| 4 | Mobile Responsive Development | 4–5 days | Mobile-optimised public detailed page |
| 5 | Backend Integration | 5–7 days | CMS wiring, admin frontend, rich-text editor, pagination |
| 6 | Testing | 1–2 days | Test execution, defect triage |
| 7 | Deployment (multiple environments) | 1 day | Staging + production deploy |
| 8 | Observations / Stabilisation | 1 week | Post-launch monitoring, polish |
| Engineering total | ~5–6.5 weeks | Platform ready to receive and publish content | |
| Content Creation (parallel track) | Months+ | 2,500+ product content packages with SEO keywords |
| Content creation is the critical path, not engineering |
| Other timing assumptions |