BrandingService
Corex\Config\Branding\BrandingService · class · Config layer
Resolves Corex’s product branding: the logo URL (config brand.logo_url override → the bundled default) and the login-logo CSS. Pure — it produces strings; the WP hooks live in AdminBranding. This is the Corex product brand (admin/login), never a client site’s look. The bundled URL is site-scoped because plugins_url() derives it from the current site’s URL. The provider injects a lazy resolver and registers this singleton with SiteScope; switching blogs clears only the memo, so the next logoUrl() call reads the new site. Project plugins with site-derived singleton values copy these steps.
Public API
Section titled “Public API”__construct(ConfigInterface $config, Closure|string $defaultLogoUrlResolver)
Section titled “__construct(ConfigInterface $config, Closure|string $defaultLogoUrlResolver)”logoUrl(): string
Section titled “logoUrl(): string”forgetSiteState(int $siteId): void
Section titled “forgetSiteState(int $siteId): void”loginCss(string $logoUrl): string
Section titled “loginCss(string $logoUrl): string”configuredFooterText(): string
Section titled “configuredFooterText(): string”configuredLoginUrl(): string
Section titled “configuredLoginUrl(): string”adminAppearance(): string
Section titled “adminAppearance(): string”The chosen CoreX admin appearance: ‘system’ (default — follows the OS scheme), ‘light’, or ‘dark’. Any unrecognized stored value resolves back to ‘system’.