Skip to content
View michael-k-levesque's full-sized avatar

Block or report michael-k-levesque

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
michael-k-levesque/README.md

Michael K. Levesque

Technical Writer | Developer Documentation | Identity & Cybersecurity

I write technical documentation and content that help people implement, understand, operate, and troubleshoot complex systems. My background in identity and access management, enterprise IT, and security informs the work; the audience's needs determine how I explain it.

The projects below demonstrate hands-on investigation, structured writing, and careful verification. I distinguish observed behavior from examples, assumptions, and guidance that has not been tested in production.

Featured work

Project What it demonstrates
Keycloak–Descope OIDC SSO documentation An independently built, non-production OIDC integration lab: verified sign-in and JIT user creation, architecture, troubleshooting evidence, and long-form technical writing samples.
Grafana + Keycloak documentation portfolio A lab-validated, 56-page documentation suite covering implementation, system architecture, service recovery, and controlled authorization changes.
AccessFlow OpenAPI documentation A fictional API documentation project featuring an OpenAPI 3.1 contract, OAuth 2.0 scopes, JSON Schema, developer guidance, examples, and automated quality checks.
Technical Documentation Lab Task-based GitHub Desktop guides, documentation review workflows, conflict resolution, and recovery procedures.

Writing and documentation focus

  • Developer-facing documentation: API references, integration guides, authentication flows, and technical explanations.
  • Operational documentation: SOPs, troubleshooting guides, runbooks, change-control procedures, and recovery guidance.
  • Technical content: Research-driven articles, educational explainers, and training-oriented scripts.
  • Documentation quality: Audience analysis, source verification, practical testing, consistent terminology, and Git-based review.

Working approach

I start with the reader's task, document prerequisites and decisions, and identify how a user can verify the expected result. For lab-based projects, I record what actually worked, what failed, and what remains untested rather than presenting a demonstration as a production-ready solution.

Connect

For technical-writing, developer-documentation, or research-based content opportunities, connect with me on LinkedIn.

These repositories contain independent portfolio projects and writing samples. References to third-party products do not imply an endorsement or client engagement.

Pinned Loading

  1. keycloak-descope-oidc-documentation keycloak-descope-oidc-documentation Public

    Lab-validated Keycloak–Descope OIDC SSO documentation covering integration, authentication, JIT provisioning, troubleshooting, and security boundaries.

    Mermaid

  2. grafana-keycloak-technical-documentation-portfolio grafana-keycloak-technical-documentation-portfolio Public

    Lab-validated Grafana and Keycloak documentation suite covering OIDC implementation, architecture, recovery, and controlled authorization change.

  3. technical-documentation-lab technical-documentation-lab Public

    Technical writing portfolio featuring task-based GitHub Desktop guides, documentation workflows, troubleshooting, and recovery procedures.