Content store support for asset management #2113
Description
What problem are we solving?
Thunder currently accepts remote URLs for logos and images (application logo URL, OU logo URL, theme logos), but does not provide an integrated content store for uploading and managing assets. This forces users to host images externally and manage URLs manually.
Who are we solving this for?
Platform administrators and application owners who need a first-class way to manage branding assets (app logo, org logo, theme images, user profile pictures) inside Thunder instead of requiring external CDN/URL hosting.
Why should we solve this now?
Support for an internal or external content store is a key UX improvement that reduces setup friction and avoids broken branding when URLs change.
Proposed solution
Introduce a content store management layer with APIs and storage adapters
Alternatives
- Keep URL-only model (current behavior) and require external hosting.
- Add UI abstraction that only rewrites URLs without storage management (not complete).