Settings page

A step of the Cloud application tree on Gradus, in the Frontend area: Second app, UI, browser tests.

A signed-in page with a section per concern, the home of everything a user can change about their account.

Usually comes after: Sign-in flow.

Leads to: Change email, Sign-in methods, Multi-factor authentication, Delete account, Profile.

Prompt for your AI assistant

Read the frontend decision record in docs/decisions. Add a settings page reached from the signed-in header, with an endpoint for the current user behind it and a section with its own address for each concern, starting with a read-only view of the user's name and email address. Settle here how every later section saves: validation on the server, a clear saved or failed message and no lost input on an error. Make it work on a phone, and add a test that a signed-out visitor is sent to sign in.

This is https://gradus.kazet.blog/tree/cloud-application/step/settings-page as plain HTML. In a browser the page also lets you mark the step forged and copy a message for your AI assistant.