Back to Tech landscape

MkDocs

Cloud & DevOps

Static documentation sites from Markdown

Official documentation (opens in a new tab)

Overview

MkDocs with Material for MkDocs publishes this repository’s implementation notes (mkdocs.yml, docs/) alongside the Blazor marketing app—Factory and client handbooks use the same Markdown-first pattern where teams want versioned docs without a CMS.

Microsoft Azure is our primary cloud: Factory templates deploy to App Service, AKS, Container Apps, and managed data services with Bicep or Pulumi, Azure DevOps pipelines, and Application Insights baked in from day one.

When engagements require hybrid or multi-cloud tooling, we adopt it with explicit landing zones, least-privilege identities, and runbooks—while keeping Azure the anchor for ConnectSoft-generated platforms.

From first commit to production dashboards, our DevOps path favors repeatable infrastructure, managed identities, and measurable SLOs—so releases stay boring in the best way.

Why we use it:

  • MkDocs Material theme and extensions aligned with repo
  • Mermaid and fenced-code support in `markdown_extensions`
  • Build in CI or locally via `requirements-docs.txt`
  • Not a runtime dependency of the marketing site host
  • Infrastructure as code with environment-specific parameters
  • Managed identities and private networking in production paths
  • Integrated CI/CD through Azure DevOps and quality gates

Ready to work with us?

Let's discuss how our team can help achieve your digital goals