Understanding Overrides

[zachdaniel]

I think we need to come up with some way to explain what overrides are available in general. The simple answer may be to direct people to the source code of the default overrides so they can see how we are doing what we're doing.

[jimsynz]

Each component documents it's overrides in the moduledocs, but I get that people may not be looking there, eg: https://ash-hq.org/docs/module/ash_authentication_phoenix/1.4.5/ashauthentication-phoenix-components-oauth2

[zachdaniel]

Yeah, the difficulty is not knowing where to look. A guide that has a link to each override and does a bit of exposition on "here is how you do custom UI stuff, and if you need structural changes then you can make your own page and use our components..." that kind of thing. I think guides are the most discoverable thing we have at the moment.

[jimsynz]

Agreed.

[frankdugan3]

After stumbling through this myself, I found the easiest thing to do was to look at the default overrides. A link to that in the docs would help a lot.

[dmitriid]

It's also unclear where and how you would use these overrides.

Since the guide only goes through autogenerated routes, the next question is... "Now what?" :)

[dmitriid]

It also doesn't help that the names don't fit on screen in docs :) Though I don't know how to fix that