HTML version of the latest Celectric_Phase1A_Submission_Pack_Clean.pdf. This page summarizes the completed Phase 1A discovery, sitemap planning, technical planning, and content/data structure definition based on the accepted quotation.
This document summarizes the Phase 1A work for the Celectric website redesign project, based on the accepted quotation. Phase 1A focuses on discovery, sitemap planning, technical planning, and content/data structure confirmation. This pack records the Phase 1A outputs, planning baseline, and recommended implementation direction established for the next project phases.
| Phase | Scope | Billing Amount |
|---|---|---|
| Phase 1A | Discovery, sitemap, technical planning, content/data structure confirmation | RM 5,000 |
The agreed direction is to redesign the Celectric website as an industrial product catalog and enquiry platform, not only as a static company profile website.
The primary conversion goal for Phase 1 is enquiry / request for quotation, not public ecommerce checkout.
| Section | Purpose |
|---|---|
| Home | Introduce Celectric, highlight product categories, brands, and enquiry CTA |
| Products | Main product catalog listing and search/filter entry point |
| Product Detail | Individual product information, specifications, datasheets, and RFQ CTA |
| Categories | Product discovery by category |
| Category Detail | Products grouped under a selected category |
| Brands | Brand listing and brand discovery |
| Brand Detail | Products grouped under a selected brand |
| Blog / Insights | Technical articles, updates, and SEO content |
| Resources / Datasheets | Product documents, datasheets, manuals, certificates, or related files |
| About | Company profile and credibility information |
| Contact / Request Quote | General enquiry and RFQ submission |
| Page Type | URL Pattern |
|---|---|
| Product listing | /products |
| Product detail | /products/{product-slug} |
| Category listing | /categories |
| Category detail | /categories/{category-slug} |
| Brand listing | /brands |
| Brand detail | /brands/{brand-slug} |
| Blog listing | /blog or /insights |
| Blog article | /blog/{article-slug} or /insights/{article-slug} |
| Contact / RFQ | /contact or /request-quote |
Each product should have one stable canonical product detail URL: /products/{product-slug}. A product may appear in multiple categories, but this should not create multiple product detail URLs.
| Layer | URL Example | Purpose | SEO Rule |
|---|---|---|---|
| Main product page | /products/ee650-airvelocity-transmitter | Main product detail page for description, brand/category browsing, datasheets, and enquiry CTA | Canonical indexable product page |
| Configurator page with params | /products/ee650-airvelocity-transmitter/configure?45793=241952&45794=297497 | Shareable configuration state that restores selected option group/value IDs | Usually not a separate SEO page; should canonical back to main product or approved model-number page |
| Direct model-number SEO page | /configuration/ee650t2j3l100p1bd5 | Clean landing page for important approved configured model numbers searched on Google | Can be indexable only for approved important model numbers |
Recommended rule: main product pages are the default canonical product URLs. Tracking parameters such as srsltid should not be included in canonical URLs. Low-value or unapproved configuration combinations should not automatically become indexable SEO pages.
A product can belong to more than one category.
Recommended relationship: products ↔ categories = many-to-many
A product belongs to one brand by default.
Recommended relationship: product → brand = belongs-to
A product can have multiple documents such as datasheet, manual, certificate, technical drawing, and brochure.
| Area | Recommended Handling |
|---|---|
| Public homepage | Static generated page |
| Product listing | Static generated page / static data where practical |
| Product detail | Static generated page |
| Category pages | Static generated page |
| Brand pages | Static generated page |
| Blog / insights | Static generated page |
| Admin dashboard | Laravel dynamic backend |
| Product/category/brand management | Laravel dynamic backend |
| RFQ submission | Laravel dynamic backend |
| Configurator data capture | Laravel dynamic backend |
| Manual publish control | Laravel dynamic backend / queue job |
| Publish status tracking | Pending, building, deployed, failed |
| Publish failure / rollback | Failed publish should not replace the current live website |
| File storage | Cloudflare R2 |
These advanced discovery features can be considered in Phase 2 after launch data is stable.
Cloudflare R2 is recommended for product images, product specification PDFs, and future private client/order documents.
| Storage Area | Purpose | Access Rule |
|---|---|---|
| product-images/ | Product images | Public / CDN-friendly |
| product-specifications/ | Datasheets, manuals, technical PDFs | Direct public download for product-related documents |
| order-documents/ | Future invoices, delivery orders, receipts, client files | Private/internal business documents |
The lightweight admin dashboard should support:
Long-form content fields should use Markdown format as the source content, not raw WYSIWYG HTML.
This document records the Phase 1A discovery, sitemap planning, technical planning, and content/data structure definition work completed for the Celectric website redesign project under the accepted quotation.
It serves as the delivery summary for the completed Phase 1A scope and as the working reference for the next implementation stages under the accepted Phase 1 direction.