Aren't these already documented in the specific pages for the AppProvider?
If we're repeating it here it's also another part of documentation that we're going to keep up to date with any upcoming changes.

Oh I see they're actually covered more in the DashboardLayout.
But maybe they could be described in the AppProvider documentation and we could link to there from here?
And keep this part in this page more generic and less specific to implementation?

We could do that to reduce maintenance load. The intention behind me doing this here is considering that this page could be something that a prospective user reads first before installing any components - so to make this document a "pitch", it should be the smoothest experience possible, which to me means fewer links, more inline demos. Let me know if that makes sense to you.

I just think we can be a bit more generic here and not cover every AppProvider prop as extensively which is a bit too much information also... So just mentioning the most important things here: probably routing, theming, authentication... in a more general way. We can have code examples /demos too, just maybe condense and stick to the most important features as opposed to listing and describing every prop.

But it's also something we can discuss and do later if it's not super consensual.

Agree with covering it more generally and not overloading with information - you're right! I'll change this a bit

I agree with Pedro, I would even remove the one line explainers for each prop and directly show a code demo like below. It should give users the basic idea.

<AppProvider
              navigation={NAVIGATION}
              branding={BRANDING}
              session={session}
              theme={theme}
              authentication={AUTHENTICATION}
            >
              {props.children}
</AppProvider>

This link is taking me to a 404 in the preview.

Instead of linking to the base concepts page, I think we should link to the App Provider component page.

Maybe we can add that for Next.js you don't need to set this up yourself. We have an AppProvider exported from @toolpad/core/nextjs that already sets it up correctly.

I could add it as a separate callout from this info callout and draw specific attention to the @toolpad/core/nextjs export