Main site guide — Frank Kienle Blue Trust System

Main site guide — Frank Kienle Blue Trust System

This file is the compact editorial and design guide for the GitHub Pages site.

Positioning

Frank Kienle publishes practical AI, analytics, and agentic automation material for operations, supply chain, sustainability/public-data analytics, and analytics translation.

The public site should feel:

  • calm,
  • credible,
  • analytical,
  • operational,
  • educational,
  • GitHub-proof-backed.

Design direction

Use the Blue Trust System:

  • Primary blue: #2F2FE4
  • Primary active: #162E93
  • Indigo: #1A1953
  • Ink: #080616
  • Soft surfaces: #F6F7FB, #F1F4FF, #E8EAFF
  • Font: Inter
  • Icons: Phosphor Icons

Avoid bright green/red defaults, generic SaaS gradients, decorative blobs, and hype-driven copy.

Content routes

  1. Homepage routes visitors into trust anchors, topics, GitHub proof, and checklist registration.
  2. Topic pages explain practical problems and link to YouTube + GitHub proof.
  3. GitHub Projects is the proof layer.
  4. Knowledge Packages is a placeholder for reviewed future assets.
  5. Register is a placeholder for the Agent Readiness Checklist flow.

Quality gate before publishing a new page

  • The page uses Blue Trust helper classes.
  • There is one clear practical problem statement.
  • Claims are grounded in public learning or GitHub artifacts.
  • CTAs are honest about status: live, draft, placeholder, or planned.
  • No employer-confidential, customer-confidential, or supplier-confidential information is included.