The Open Podcast API server is primarily headless. However, a frontend is needed for simple things like displaying a login form/OAuth permission form. In addition, we may want to display some simple information to users in a web interface for testing purposes and eventual deployment purposes such as:
- A list of subscriptions.
- Information about specific subscriptions.
- Actions on subscriptions (e.g. unsubscribe, subscribe)
- Popular subscriptions on the server.
- User settings (e.g. update password, change username, update email address, delete account).
This is dependent on implementing and extending #2. Currently, the server supports authentication using Spring Security and form-based login. This is good enough for login, but we will need to style the template to fit with the rest of the interface. We will also need to implement a better password encoder (see Spring Security docs about DelegatingPasswordEncoder).
This user interface SHOULD work without JavaScript and MAY be progressively enhanced using HTMX.
The Open Podcast API server is primarily headless. However, a frontend is needed for simple things like displaying a login form/OAuth permission form. In addition, we may want to display some simple information to users in a web interface for testing purposes and eventual deployment purposes such as:
This is dependent on implementing and extending #2. Currently, the server supports authentication using Spring Security and form-based login. This is good enough for login, but we will need to style the template to fit with the rest of the interface. We will also need to implement a better password encoder (see Spring Security docs about
DelegatingPasswordEncoder).This user interface SHOULD work without JavaScript and MAY be progressively enhanced using HTMX.