Each link below renders one of the ePDS preview pages with fixture data, so you can iterate on your client's branding.css without walking through the full OAuth flow. Routes from both services are listed here; links under pds-core point to the other service and don't pick up the client-metadata URL below — enter it once per service.
The trusted-clients check still applies: your URL must be on PDS_OAUTH_TRUSTED_CLIENTS for its CSS to be injected, exactly as in a real OAuth flow. Leave the field blank to render the pages unbranded (baseline).
Alternatively, skip the field and append this query string to any of the links above:
?client_id=<URL-of-your-client-metadata.json>Preview routes always re-fetch client metadata, so edits to your branding.css show up on the next refresh here. The list below reflects what real OAuth flows are still seeing — each entry is cached for 10 minutes from its last real fetch, so until it expires, real users won't pick up your changes yet.