Investigate to which extent we may make our components more easily usable with component frameworks like React, Vue, Svelte, or Angular. Depending of what we want to facilitate, we could then look at:
if there's anything to do to limit having to re-implement the HTML rendering
if there's anything to do so our components integrate nicely with the lifecycle of these libraries (especially when re-rendering occurs)
Why
Frameworks like React, Vue, Svelte or Angular may be a valid technical choice (provided progressive enhancement and performance are kept in mind when using them). However:
they require completely porting our templates to these frameworks syntax, which is not only a heavy initial effort, but has maintenance costs to keep up to date when we change our templates
while our components can be initialised in these frameworks, they expect the page to be torn down at each navigation, which is not the case when using JavaScript frameworks, which can cause issues when components get re-rendered because of state changes.
Who needs to work on this
Developers
Who needs to review this
Developers
Done when
[ ] We've defined more clearly which questions we'd want to answer
[ ] We've run spikes to get answers to these questions
What
Investigate to which extent we may make our components more easily usable with component frameworks like React, Vue, Svelte, or Angular. Depending of what we want to facilitate, we could then look at:
Why
Frameworks like React, Vue, Svelte or Angular may be a valid technical choice (provided progressive enhancement and performance are kept in mind when using them). However:
Who needs to work on this
Developers
Who needs to review this
Developers
Done when