I built a better documentation site for oidc-provider

While building a production-ready OpenID Connect server with oidc-provider, I ran into a recurring issue: 👉 the documentation is powerful, but not easy to navigate. So I built this: 🔗 https://oidc-provider.dev/ The problem oidc-provider has excellent documentation, but it is: spread across multiple files (README, docs/, events, changelog) not easily browsable hard to search or explore progressively This makes onboarding and day-to-day usage slower than it should be. The solution I created a dedicated documentation site that is: 📚 fully browsable (multi-page navigation) 🔍 searchable 🧭 easier to explore than raw Markdown 🗂 structured by topics Always in sync with upstream The key design constraint was: never diverge from the official documentation So the site is: automatically generated from official sources: README docs/* CHANGELOG events.md continuously synced via GitHub Actions Any update in the upstream repository is reflected automatically. Why this matters oidc-provider is a low-le