---
title: "Discussion on \"Building a per-repo wiki that actually gets read\" | Hashnode"
description: "Discussion on \"Building a per-repo wiki that actually gets read\". Building a per-repo wiki that actually gets read\n\n\nTL;DR - Our docs were not missing. They were in READMEs, internal docs folders, and even in the comments of our CI/CD workflows. The CI/CD was fully automated. And yet one specific teammate kept ping..."
url: "https://hashnode.com/posts/building-a-per-repo-wiki-that-actually-gets-read/69ebb703394475c6d02d5efa"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Building a per-repo wiki that actually gets read](https://vineethnk.hashnode.dev/building-a-per-repo-wiki-that-actually-gets-read?utm_source=hashnode&utm_medium=feed)

Building a per-repo wiki that actually gets read TL;DR - Our docs were not missing. They were in READMEs, internal docs folders, and even in the comments of our CI/CD workflows. The CI/CD was fully automated. And yet one specific teammate kept ping...

Apr 24 · 16 min read · vineethnk.hashnode.dev  
Read the article

-   [#team-process](https://hashnode.com/tag/team-process)
-   [#devops](https://hashnode.com/tag/devops)
-   [#docs](https://hashnode.com/tag/docs)
-   [#github-actions](https://hashnode.com/tag/github-actions)
-   [#onboarding](https://hashnode.com/tag/onboarding)

## Written by

[Vineeth N K](https://hashnode.com/@vnknotes)

@vnknotes

  
[View profile](https://hashnode.com/@vnknotes)

What I learned the hard way. So you do not have to.

Hi, I am Vineeth (VNK). I am a software developer and DevOps engineer based in Kochi, India. I work across backend (Node.js, NestJS, PHP), infrastructure (Docker, MySQL, Linux), and frontend (Vue, React). I am currently building and operating products with BEO, where I do everything from architecture decisions to staging deployments to fixing the things that break at 9 PM on a Friday. I write about real problems from real work - the kind of things you do not find in tutorials. Production incidents, hard-won architecture lessons, team and process notes, and the occasional opinion piece. If something I shipped, broke, or learned might save someone else half a day, it goes here. No fluff. No ghostwritten thought leadership. Just notes from the terminal.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.