Presentation outlines for an Introduction to Cloud Computing course aimed at computer science students. Outlines are structured for import into gamma.app to generate polished slide decks.
- Legacy presentations (legacy/) contain the original slide decks (outlines + exported PDFs) that served as source material.
- Research paper (papers/) — the legacy content was fed into Google NotebookLM, which synthesized it into a structured academic paper (paradigm_shift_to_modern_cloud_computing.md). This paper serves as a consolidated reference covering cloud fundamentals, economics, architecture patterns, DevOps practices, and real-world case studies.
- REVIEWER.md defines the review criteria — a rubric written from the perspective of a senior cloud architect. It evaluates outlines against seven dimensions: foundational principles, DevOps/Agile as practice, the "vibe coding" reality check, real-world anchoring, security, structure/flow, and gaps.
- New outlines (outlines/) are revised or freshly written presentations that satisfy the reviewer criteria. Each outline is structured for gamma.app: clear sections, discrete slide-level topics, ~25 slides, with an explicit narrative arc.
cloud-presentations/
├── REVIEWER.md # Review rubric (senior cloud architect perspective)
├── legacy/
│ ├── ci-cd-outline.md # Original CI/CD outline
│ ├── monoliths-to-microservices-outline.md # Original architecture outline
│ └── pdf/
│ ├── ci-cd.pptx.pdf # Exported legacy CI/CD deck
│ └── monoliths-to-microservices.pptx.pdf # Exported legacy architecture deck
├── outlines/
│ ├── cloud-101-outline.md # Intro to Cloud Computing (~25 slides)
│ ├── cloud-architecture-outline.md # From Monoliths to Modern Systems (~25 slides)
│ └── ci-cd-devops-outline.md # CI/CD and DevOps in Practice (~25 slides)
└── papers/
└── paradigm-shift-to-modern-cloud-computing.md # Research paper synthesized from legacy content
| File |
Topic |
Narrative arc |
| cloud-101-outline.md |
Introduction to Cloud Computing |
Why cloud exists → How it works → How to use it responsibly → Cost → Failure modes |
| cloud-architecture-outline.md |
From Monoliths to Modern Systems |
Why architecture matters → Monoliths → Growing pains → Microservices → Trade-offs → Case study |
| ci-cd-devops-outline.md |
CI/CD and DevOps in Practice |
Why waterfall failed → Agile mindset → DevOps culture → CI/CD mechanics → IaC → Lab |
Reviewing an existing outline
Feed the outline to an LLM with REVIEWER.md as the system prompt (or paste both into a chat). The reviewer will return structured feedback: overall assessment, section-by-section notes, structural suggestions, and top 3 priorities.
- Start from a legacy outline or topic brief.
- Review it against REVIEWER.md to identify gaps.
- Write or revise the outline following the gamma.app structure conventions (see below).
- Save to outlines/.
- Open gamma.app and choose Import → Paste text.
- Paste the outline markdown.
- Gamma will generate slides from the heading structure. Each ## Slide N: Title block becomes one slide.
- Header: target audience, slide count, narrative arc at the top of each file.
- Slide headings: ## Slide N: Title — one concept per slide.
- Content per slide: bullet points, a one-line speaker note or key takeaway, and a [Visual] cue for gamma.app image generation.
- Depth: aim for ~25 slides. Avoid deep nesting (gamma.app handles two heading levels cleanly).
- Tone: practical over theoretical. War stories and failure modes belong alongside happy paths.