Content
View differences
Updated by Alexander Coles 3 days ago
**Goals:**
* Evaluate how much of the existing Boards codebase we can re-use – with the objective of **shipping user-facing features much faster**: in this case, a rudimentary UI for status mapping (see <mention class="mention" data-id="71104" data-type="work_package" data-text="#71104">#71104</mention> )
* **Continue evaluating Claude** for development tasks, with a particular emphasis
* on well-tested, production-quality code
* getting to know the Angular CLI MCP for Angular tasks.
* **Learn Primer React** - and evaluate how it interops with Primer's View Component implementation. Also, how we might be able to "hedge" and take advantage of the React library given PVC's effective. deprecation. _This should feed into discussions at D-Team offsite!_
* Continue evaluating how to make **React and Angular play nicely**. (following on from/or possibly superceding <mention class="mention" data-id="66983" data-type="work_package" data-text="#66983">#66983</mention> )
**Constraints**:
* Spend minimal human dev hours on this until we get stakeholder consensus on future frontend architecture and framework choices. dev path.
* Keep a Turbo Boards rewrite on the table. Existing UI components.
* Use existing UI components, albeit While the React implementations thereof.
* Be first iteration might not be good enough to be shippable (eventually) - shippable, don't create something completely throw-away (i.e. not "vibe coded") _This may be considered an anti-pattern for spikes, but there are already a couple open GitHub Pull Requests that show React integration that can be considered throw-away._
* Evaluate how much of the existing Boards codebase we can re-use – with the objective of **shipping user-facing features much faster**: in this case, a rudimentary UI for status mapping (see <mention class="mention" data-id="71104" data-type="work_package" data-text="#71104">#71104</mention> )
* **Continue evaluating Claude** for development tasks, with a particular emphasis
* on well-tested, production-quality code
* getting to know the Angular CLI MCP for Angular tasks.
* **Learn Primer React** - and evaluate how it interops with Primer's View Component implementation. Also, how we might be able to "hedge" and take advantage of the React library given PVC's effective. deprecation. _This should feed into discussions at D-Team offsite!_
* Continue evaluating how to make **React and Angular play nicely**. (following on from/or possibly superceding <mention class="mention" data-id="66983" data-type="work_package" data-text="#66983">#66983</mention> )
**Constraints**:
* Spend minimal human dev hours on this until we get stakeholder consensus on future frontend architecture and framework choices.
* Keep a Turbo Boards rewrite on the table.
* Use existing UI components, albeit
* Be