How ernyoke/certified-aws-solutions-architect-professional works
Project type and purpose
• This is a documentation site (AWS Solutions Architect Pro notes), organized as Markdown files plus images and a _config.yml file (typical of Jekyll or similar static‐site generators).
• The purpose is to generate a browsable website or PDF of categorized AWS‐service notes.
Main components
a. Content Source
• Directories 01-accounts/, 02-identity/, … through 16-other/ each contain .md files and images.
• The README.md and _config.yml provide global site metadata and navigation.
b. Static‐Site Generator
• A tool such as Jekyll, Hugo, or MkDocs that reads Markdown + config and applies templates.
c. Templates & Layouts (if present)
• In absence of explicit template folders, note “default theme” as part of the build.
d. Output
e. Hosting & Distribution
• For example, GitHub Pages, AWS S3 + CloudFront, or Netlify.
f. Optional CI/CD Pipeline
Relationships and interactions
• Developers commit Markdown changes to a Git repo.
• A CI/CD pipeline (optional) triggers the SSG to run.
• The build engine transforms content + config into static assets.
• The pipeline or manual process deploys static assets to a hosting service.
• A CDN (CloudFront or GitHub Pages) caches and serves content to end users.
Architectural patterns & design principles
• Separation of concerns:
• Content ↔ Build engine ↔ Hosting ↔ Delivery
• Immutable artifacts:
• Once HTML is generated, it’s static and easily cachable.
• Modularity:
• Each top‐level folder (e.g., 03-networking/) is a module that maps to a section in the site.
Technologies & frameworks
• Markdown for content
• _config.yml for global settings (Jekyll)
• Jekyll (or Hugo/MkDocs) as SSG
• GitHub (or GitLab) as version control
• CI/CD: GitHub Actions, Travis CI, AWS CodeBuild (if used)
• Hosting: GitHub Pages or AWS S3 + CloudFront