According to https://hexdocs.pm/ash_authentication_phoenix/AshAuthentication.Phoenix.html there are several ways to customise the authentication process: 1. Use the generic sign-in liveview - AshAuthentication.Phoenix.SignInLive.Apply 2. overrides using AshAuthentication.Phoenix.Overrides to set your own CSS classes for all components. 3. Build your own sign-in pages using the pre-defined components. 4. Build your own sign-in pages using the generated auth routes.
Are there any examples, especially for 3 and 4?
Do I even need AshAuthentication.Phoenix in these cases?
Furthermore, out of curiosity, am I able to use the standard
phx.gen.auth
phx.gen.auth
from phoenix and point to an ash resource instead of an ecto schema?
The Elixir backend framework for unparalleled productivity. Declarative tools that let you stop wasting time. Use with Phoenix LiveView or build APIs in minutes for your front-end of choice.