МКEN

Оригинална техничка референца на англиски. Практични упатства на македонски →

Bi-Dash visual identity

The Rising Signal mark uses three ascending, faceted data segments and a separate yellow dash. It has no letter B, enclosing square or stock icon. The mark represents data becoming a clearer signal. The horizontal wordmark is used on account screens; the compact mark is used in navigation, loading screens, notifications, shared dashboards and browser tabs.

RoleColor
Primary / action#2563EB
Small accent#FACC15
Navigation / ink#191C22
Blue on dark backgrounds#60A5FA
Canvas#F4F6FA

Product line: Your data. A clearer direction.

Editable SVG masters, a dark-background variant, a monochrome mark, PNG icons, an ICO and a preview are under branding/. Production vectors are under client/app/assets/images/. Keep the mark’s proportions, allow at least 8/64 of its width as clear space and use the light-blue variant on dark backgrounds. Minimum icon size: 16 px. Do not enclose the mark in a blue square. Semantic success, warning and error colors remain independent of the brand palette.

Copyright (c) 2026 Slavcho Spasenoski applies to original Bi-Dash contributions to the extent protected by applicable law; see COPYRIGHT.md and NOTICE. This custom vector design is not a trademark registration or a guarantee that no similar mark exists. Third-party fonts, screenshots, upstream code and customer quotations retain their own rights.

Technical package names, environment variables, API routes, persisted keys, database tables and Docker volumes retain upstream compatibility. The rebrand does not change source credentials, connections, accounts or queries. Upstream copyright notices, original changelogs, the archived README and historical quotations keep their actual attribution. They must not be represented as Bi-Dash’s original work or endorsements.

The documentation/marketing source is not a published Bi-Dash service. Set BIDASH_SITE_URL before hosting it; its default .example origin is deliberately not a claimed production domain. Archived upstream case studies are labeled as historical.

Validation on 2026-11-08: production application image built; 28 local AI/settings tests and eight notification integration tests passed, plus the existing rebranded Asana payload assertion with mocked HTTP. The documentation site built 131 pages on Linux. Edge checks verified the new login/navigation assets, favicon, mobile width, copyright notices and downloaded license files. Original upstream license terms, README.upstream.md and third-party license files were compared with the recorded source and retained. Main database credentials and data-source settings were not changed by this rebrand.

The four inherited empty-state illustrations were replaced with new SVGs because their separate upstream notice disallowed fork distribution. Their original notice is preserved as provenance, not rewritten as a Bi-Dash license. See COPYRIGHT.md for the scope of current-tree replacement and historical snapshots.