Telescope 2.0 Planning

Themes

Front-end
- Port front-end from Gatsby to Next
- Make the app installable as a Progressive Web App (PWA) on mobile
- Improve the Admin dashboard(s) experience: managing feeds, users, posts
- Improve UX for adding new feeds (e.g., automatic RSS feed discovery from blog URL)
- Improve accessibility
- Better UX for search
Back-end
- Migrate User data and Feed storage out of Redis and into to a more suitable database. MongoDB? Fauna? Something we run in a container?
- Fix our Redis data corruption when we lose power on production
- Migrate away from the Wiki Feed List as the source of truth, and use the Feeds from the database
- Build out our error/log reporting that we started with Kibana
- Continue building on the improvements we've started with Search (e.g., autocomplete for author names)
- JSDOC, jsconfig.json typings for node code
Security
- Modify our Authentication/Authorization system to allow token based authentication
Features
- Figure out how to integrate user GitHub activity and contributions (PRs)
- Prototype having Twitch Streams, YouTube Live, and other "Telescope Podcast" experiences. I think this idea is great, but I'm still waiting to see if the students agree. Not everyone is comfortable to stream their work. Maybe we'll do it, maybe not.
- Analytics
- Swag? We have talked about having shirts, mugs, and stickers in the past, but it hasn't happened yet. Maybe for the 2.0?
Technical Debt
- Improve developer experience
- More and better automated tests
- Improve docs and integrate with front-end (MDX pages)
- Refactor and Simplify back-end code
- Split code into separate pieces and properly Dockerize: REST API, deployment server, feed processor, front-end