Let’s collect some high-level themes for arch/infrastructure work that we should consider for Teak and after.
These are things that wouldn’t necessarily come up from the product viewpoint. So there’s no need to put things like, “Make video subtitles work properly”. These are also meant to be fairly broad topics, with the idea that we’ll groom them into more actionable stories later.
Goals
Get an early start on some of these initiatives if possible.
Make sure we have these things in mind as we’re building new features like Units, so that we can interleave some of that work in an intelligent way.
React Query
Should we be planning to move from Redux -> React Query?
How disruptive would this be, and what timeline could we achieve it on?
Would this make our frontend less chatty (we throw a lot of requests around)
Removing XBlock-orientation
We use “blocks” in the API a lot, but some things should be generically applicable to components (e.g. file upload, tagging), some are applicable to any publishable thing (e.g. “publish”), and some are specific to XBlocks.
Extensibility
We should work as much of our own code into Slots and other extension points–at least as much as is practical.
Dev Documentation
Learning Core needs doc generation.
Likewise with Libraries in general.