How praveen1994dec/knowledge_base works
• Topic-Specific Modules: Around the central node, create individual components for each major category (AWS, Docker, GIT, Helm, Jenkins, Linux, Monitoring, Python, REST_API, Shell_Scripting, Terraform, and kubernetes). These modules reflect the top-level directories in the file tree.
• Auxiliary/Other Files: Optionally include nodes for standalone files like “hello.txt” and “test.py” if they play a role in the reference structure or are indicative of scripts for processing or testing.
Architectural Patterns and Principles
• Modular Design: Emphasize that the repository is organized in a modular fashion where each tool or technology is isolated in its own directory, making it easy to update or expand without affecting other sections.
• Clear Separation of Concerns: By separating documentation by topic (e.g., Docker vs. Jenkins), the design showcases independent modules that serve distinct areas of knowledge.
Relevant Technologies/Tools
• Although this is not a full-stack application, note that the repository includes configuration and cheat sheet documents for modern DevOps tools. Include small annotations/bubbles near each module that identify the technology (e.g., “Docker”, “Kubernetes”, “Terraform”) so that viewers understand the technical domains.