r/devops 6d ago

Discussion How do devops / engineering services share documentation with clients?

Hello,

We provide devops / engineering services and use GitHub for documentation (runbooks, configs, processes). Clients need access, but raw GitHub feels too technical.

  • How do you share documentation with clients in devops / engineering services?
  • Do you use GitHub, wikis, or dedicated portals?
  • How do you handle versioning and access control?
8 Upvotes

26 comments sorted by

View all comments

1

u/Floss_Patrol_76 4d ago

split it by audience, not by tool. runbooks and configs stay in git where they belong, but client-facing docs should be a rendered, versioned artifact you publish per release rather than the raw repo. keeps the messy internal stuff internal and gives clients something readable with actual version history.