macos-setup
🐱 Source ☕️ Java SampleGo Sample Angular Sample
  • Mac Setup
  • Getting Started
    • Xcode
    • Homebrew
    • System Preferences
    • Essentials
    • Dotfiles
  • Applications
    • Ghostty
    • Sublime-text
    • JetBrains
    • VSCode
    • Xcode
    • Marta
    • Benthos
    • OrbStack
    • Traefik
    • n8n
  • Platforms
    • Java
    • Node
      • Bub
      • NPM
      • PNPM
      • Turborepo
    • GoLang
    • Rust
    • Python
      • Agno AI
  • DevOps
    • Development Workflow
      • Git
        • GitHub CLL
      • GitOps
      • Documentation
      • mkcert
      • YubiKey
    • Monorepo
    • dnsmasq
    • Docker
    • Skaffold
    • Kubernetes
    • Helm
    • Kustomize
    • kustomizer
    • Terraform
    • Security
    • Cloud
      • gcloud
      • azure
      • aws
  • Tips
    • Git
    • MacOS
Powered by GitBook
On this page
  • Markdown
  • Folding area
  • diff
  • Checkbox
  • Table of contents
  • Image adjustment
  • Diagrams
  • Footnote
  • Reference

Was this helpful?

Edit on GitHub
  1. DevOps
  2. Development Workflow

Documentation

PreviousGitOpsNextmkcert

Last updated 2 years ago

Was this helpful?

Documentation is key for any project success. When team members move to different projects, the will be lost, and it would be hard for new maintainers keep the project on track as per the original Roadmap. We believe in philosophy and keep related documents close to code in the same repository.

Docs should be organized under docs folder in the root of the repo. We recommend for writing documents and leverage and to embed diagrams directly into Markdown files.

Recommended minimal documentation for each project:

  • README.md - Should contain Project goals, big picture, list of features, developer's workflow to contribute to repo.

  • to keep tracking releases, milestones, features and project status.

  • Roadmap should include short and long term goals.

  • Changelog - Automatically changelog as part for release process.

  • - file contain resources who own specific module in the repository and who should review before PRs are merged.

  • Architecture Decision Record - is a document that captures an important architectural decision made along with its context and consequences.

  • Style Guide - Coding Style Guide

Markdown

Extra GitHub Markdown tricks

Folding area

<details>
<summary>Fold/Open</summary>
Folded content
</details>
Fold/Open

Folded content

diff

function compare (num1, num2) {
-  return ALL_SAME;
+  return NOT_SAME;
}
function compare (num1, num2) {
-  return ALL_SAME;
+  return NOT_SAME;
}

Checkbox

Future improvements:
- [ ] Point 1
- [ ] Point 2
- [x] Point 3

Future improvements:

Table of contents

To generate it, markdown provides a shortcut: An easy auto-generation. All the titles defined with #will be edited into the table of contents if the [TOC] is added in the appropriate place.

Image adjustment

Size adjustment

<img src='https://tomcat.apache.org/res/images/tomcat.png' width=300px height=200px />

Image position control

<div align="center">
  <img src="https://tomcat.apache.org/res/images/tomcat.png" align="center">
</div>

Diagrams

mermaid

graph LR;
    subgraph µServices
    A(fa:fa-user Account µS)--gRPC-->G(Greeter µS) & E(Emailer µS);
    A & G & E -.-> L[Logger]
    end
    A ==lookup==> SR[[fa:fa-database Service Registry]];
    style SR fill:#f9f,stroke:#333,stroke-width:4px
graph LR;
    subgraph µServices
    A(fa:fa-user Account µS)--gRPC-->G(Greeter µS) & E(Emailer µS);
    A & G & E -.-> L[Logger]
    end
    A ==lookup==> SR[[fa:fa-database Service Registry]];
    style SR fill:#f9f,stroke:#333,stroke-width:4px

Draw.io

<div align="center">
  <img src="../../images/deployment.drawio.svg" width="60%" align="center">
</div>

Footnote

Here need a footnote[^noteID1].

[^noteID1]: Here is the quote for ID1.

Reference

Tribal Knowledge
Docs as Code
GitHub Flavored Markdown
draw.io
Mermaid
Project Boards
generate
Code Owners
CODEOWNERS
(ADR)
The Magical Markdown I Bet You Don’t Know