Site Rebuild Decision — Elementor (2026-02-02)
Overview
During the [1], the team decided to rebuild the New Dawn site from scratch using Elementor. The existing build had performance issues and was slowing development velocity. A full rebuild was deemed faster and cleaner than continuing to patch the current implementation.
The next client-facing meeting is scheduled for 2026-02-13, giving the team approximately 11 days to align internally before presenting the plan to the client.
Decision
Rebuild the New Dawn site from scratch using Elementor.
| Attribute | Detail |
|---|---|
| Decision date | 2026-02-02 |
| Decision maker | Sebastian Gant (AM), with Melissa Cusumano |
| Technical lead | Isahaque Mahmud |
| Next client meeting | 2026-02-13 |
Rationale
- The existing build had performance issues that were degrading the site.
- Development was moving slower than expected under the previous approach — Isahaque was noted as moving slowly in the prior framework.
- Elementor allows for faster page/template creation and a cleaner starting point.
- The site is not highly complex; it was previously templated, so a rebuild is considered low-risk and faster than remediation.
"It should be kind of quicker too, right? Because like, I think it was, he was moving slow in the other field there." — Sebastian Gant
"He'll just have to now create the templates or the pages. It's not really a complex… it was a templated website." — Melissa Cusumano
Action Items
- [ ] Sebastian Gant — Sync with Isahaque Mahmud on rebuild plan, scope, and timeline before the 2026-02-13 client meeting.
- [ ] Sebastian Gant — Email the client (Katie) after the internal sync to communicate the rebuild approach.
- [ ] Isahaque Mahmud — Begin Elementor rebuild once aligned with Sebastian on scope.
Related
- [2]
- [3]