What problem does this solve?
The Resources tab displays playlists and videos in the order they were added. Users who have saved multiple playlists across different subjects -- for example, flight mechanics, propulsion, and structures -- have no way to reorganize them. As the list grows, frequently used resources get buried and users have to scroll through everything to find what they need.
Describe the feature
Allow users to reorder their saved resources by dragging and dropping them into a preferred order. The order should persist across page refreshes via localStorage, the same way resources themselves are already persisted.
A drag handle icon on each resource row would indicate it is draggable. No additional UI beyond that should be needed.
Why does this fit the project?
The reordering state would be stored entirely in localStorage alongside the existing resource data in STORAGE_KEYS (src/lib/storage.ts). No backend, no server, no accounts required. It is a pure client-side enhancement that fits the local-first design of the app.
Alternatives you considered
Manually deleting and re-adding resources in the preferred order -- but this loses watch state and done flags tied to each resource, so it is not a viable workaround.
Additional context
The existing resource data structure in src/features/resources/ResourcesView.tsx already holds resources as an array, so order is implicitly tracked. The change would be to make that order user-controlled rather than append-only.
What problem does this solve?
The Resources tab displays playlists and videos in the order they were added. Users who have saved multiple playlists across different subjects -- for example, flight mechanics, propulsion, and structures -- have no way to reorganize them. As the list grows, frequently used resources get buried and users have to scroll through everything to find what they need.
Describe the feature
Allow users to reorder their saved resources by dragging and dropping them into a preferred order. The order should persist across page refreshes via
localStorage, the same way resources themselves are already persisted.A drag handle icon on each resource row would indicate it is draggable. No additional UI beyond that should be needed.
Why does this fit the project?
The reordering state would be stored entirely in
localStoragealongside the existing resource data inSTORAGE_KEYS(src/lib/storage.ts). No backend, no server, no accounts required. It is a pure client-side enhancement that fits the local-first design of the app.Alternatives you considered
Manually deleting and re-adding resources in the preferred order -- but this loses watch state and done flags tied to each resource, so it is not a viable workaround.
Additional context
The existing resource data structure in
src/features/resources/ResourcesView.tsxalready holds resources as an array, so order is implicitly tracked. The change would be to make that order user-controlled rather than append-only.