Logo system
Use the full WBAMS wordmark in frontend and control-area headers and footers. The icon alone is reserved for favicons, compact launchers, application tiles, and spaces where the wordmark cannot remain legible. The icon should visually align with the height of the WBAMS wordmark.
Light and dark assets
wbams-logo-on-light.pngfor light surfaces.wbams-logo-on-dark.pngfor dark surfaces.- Icon sizes from 16×16 through 1024×1024 for browsers, devices, and applications.
Footer logo assets
Open CMS → Settings → Footer Settings → Brand Identity. The default Same as Header choice keeps the header light/dark branding pair synchronized with the footer. Choose Different Footer Logo only when the footer needs a distinct treatment, then select the light footer logo and optional dark footer logo from the Media Library.
WBAMS preserves safe output when custom fields are incomplete. If custom mode has no light footer logo, Serepok uses the header branding pair. If the custom light logo exists but the dark logo is blank, Serepok uses the custom light logo in both color modes. Keep the custom light asset legible on both surfaces when relying on that fallback.
Fresh installs and upgrades default to Same as Header. The 1.1.1 updater adds missing footer-logo settings idempotently and preserves existing setting values when it is run again.
Media library
The CMS media library supports uploaded files, SVG assets, existing media, and premade illustrations. Select an asset, verify its preview, add descriptive alternative text, and use optimized dimensions. Keep filenames lowercase and descriptive.
Open it from Content Manager › Media Library, or from any picture field. Select a file to see its details at the bottom of the library, with these actions:
Rename and Delete are offered for Uploads and Site media only, to administrators whose role may configure general settings or manage the knowledgebase. Files in the Stock library and the illustrations ship with WBAMS and can be viewed and copied, not renamed or deleted.
WBAMS image principles
Images should explain the product: connected customer records, plans, invoices, payments, automation, support, and operational signals. Avoid generic decoration that could describe any software. Prefer clear data flows, connected systems, visible outcomes, and trustworthy customer operations.
Keep source masters outside the public media library. Optimize a copy for delivery, record usage, and verify light/dark contrast before replacing a global logo.
The client theme
Draisap is the customer-facing theme and the only order form the product ships. It is self-contained: as of 1.5.0 it inherits from nothing, having previously extended a standard-checkout form that has been removed.
An update replaces the files it ships. Work in a copy and the updater leaves it alone; edit the original and your changes are what the release notes call “overwritten”.