How chu292/security_operations_center works
Project type and purpose
• This is not a typical “application” but a large, hierarchical collection of educational resources (Markdown lessons, PDFs, lab solutions, images) covering networking, OS, security, web, etc.
• Purpose: serve as a centralized repository of course materials and labs that can be viewed or published as documentation.
File structure
• Top-level directories represent different courses or topics (e.g., Computer_networks_and_security_control_in_computer_networks, How_The_Web_Works, Linux_Fundamentals, ITMO, Theory, Windows_Fundamentals).
• Under each, you have subdirectories for lectures, labs, images and README files.
• There are no source code modules to compile; it’s purely content files and assets.
README
• The README is a humorous title banner (“Các Bài học của CVĐ và ChatGPT plus của anh ấy”) indicating a personal collection of lessons.
• No technical stack or architecture details—so we treat this as a static content repository.
a. Main components:
• Content Repository: Git repository holding Markdown, PDFs, images.
• Static Site Generator (SSG): tool such as MkDocs, Hugo or GitBook that converts content into HTML.
• CI/CD Pipeline: e.g., GitHub Actions or GitLab CI to build the site on each commit.
• Hosting Service: GitHub Pages, Netlify, or S3+CloudFront for static site hosting.
• CDN: delivers static assets globally.
• End Users: students or instructors accessing the published site via browser.
b. Relationships & data flow:
1. Developer (or content author) commits changes to the Git repo.
2. CI/CD pipeline picks up the commit and invokes the SSG.
3. SSG reads the file tree (content + images) and produces a static site.
4. CI/CD deploys the generated HTML/CSS/JS to the Hosting Service.
5. Hosting Service invalidates the CDN cache (optional).
6. End User requests pages; DNS directs to CDN edge; CDN serves cached assets or fetches them from origin.
c. Architectural patterns & design principles:
• Separation of concerns: content (Markdown) → presentation (SSG) → delivery (hosting/CDN).
• Immutable artifact: every build produces a set of static files that never change once published.
• Continuous deployment ensures published site always matches the repo.
d. Key technologies you might choose:
• Git/GitHub for version control.
• MkDocs or Hugo for static generation.
• GitHub Actions or Netlify for CI/CD.
• GitHub Pages, Netlify, AWS S3 + CloudFront for hosting.
• Optional search engine like Algolia DocSearch.