Uploaded brand assets now install
You could always upload a logo and a hero image during the build. What was missing was the last step: putting them onto the site. That step now exists, so the asset you upload is the asset that appears.
Uploads are scoped to your organization
Every file you upload is now stored under your organization, and the portal checks that ownership both when the file is uploaded and again later when it is read back to install it.
The reason for checking twice: a record stored before this rule existed should not be trusted simply because it is old. If it cannot prove who it belongs to, it is refused rather than used.
Two fixes for images that installed but never appeared
Both of these were the worst kind of bug. Every automated check passed, the build reported success, and the visitor saw nothing.
- Background images that resolved to nothing. An image referenced from custom stylesheets was being looked for in the wrong place, so it silently failed to load.
- Vector logos that rendered invisible. A gradient or pattern fill inside an uploaded SVG could resolve to nothing, drawing the shape with no paint at all.
Both are now caught at the point the asset is installed, and the error names the exact property at fault instead of failing quietly.