Decisions — Linc-Website

Durable decisions and their rationale. One decision per bullet.

  • Positioning is SaaS-first; Linc no longer offers its own hosted environment — the vast majority of clients run Business Central on Microsoft’s cloud (SaaS), so documentation defaults to Cloud and treats On-premises / Privately Hosted as a small secondary case.
  • Use “Entra ID (Microsoft 365)” terminology, not “Azure AD” / “Office365” — reflects Microsoft’s current naming and the enterprise/Microsoft-aligned brand.
  • The Linc logo and its palette are the strict design bible — designs must use only the canonical linc.co.za cyans (#009bc2, #00aeef, #067b9e, #69b0c6); gold #c49a6c is a hairline accent only.
  • Do not borrow branding from the sub-brands — ProduceLinc / WineLinc / CommLinc / FarmLinc colours and framing must not bleed into linc.co.za; sub-brands are listed as products but styled with the single brand cyan. (This was an explicit correction after a first redesign pass pulled sub-brand colours in.)
  • Brand feel target is “enterprise-trustworthy / Microsoft-aligned.”
  • Edit the markdown source, not the built HTML — for pages like audit-questions, the .html is generated from the .md; changes go in the .md.
  • just-the-docs remote_theme is intentionally disabled — commented out in _config.yml due to local-dev SSL issues; content pages are styled with Bulma + inline CSS in _includes/linc_head.html instead.
  • Global/shared styles live in the inline <style> block in _includes/linc_head.html — not per-page.
  • Deploy via GitHub Pages on the apex domain — CNAME pins linc.co.za; pushing the default branch builds and publishes.