# Azure AI Services — A DCSA's Presentation Journal

> The running notebook of a **Digital Cloud Solution Architect** learning, distilling, and presenting **Azure AI Services** — one customer briefing at a time.

Every time I go deep on an Azure AI service to brief a customer, I turn what I learned into a clean, cinematic deck and drop it here. Think of this as a **presentation diary**: each entry is a self-contained `index.html` — no build step, no dependencies, works offline, and publishes as its own page on GitHub Pages.

The goal is simple: **grounded in the docs, honest about limits, and good enough to put in front of a real customer.**

> Author: **Kardel Rüveyda Çetin** · Digital Cloud Solution Architect
> 🌐 Live: <https://kardelruveyda.github.io/azure-ai-services-presentations/>

---

## The journal so far

| # | Entry | Status | What it covers | Live |
|---|-------|--------|----------------|------|
| 1 | **Azure AI Content Safety** | ✅ Ready | Harm categories & severity, Prompt Shields, Groundedness, Protected Material, real-world scenarios | [Open ↗](https://kardelruveyda.github.io/azure-ai-services-presentations/azure-ai-content-safety/) |
| 2 | Azure AI Foundry | 🕓 Next up | Agents, models, evaluation & deployment | — |
| 3 | Azure AI Search | 🕓 Backlog | Vector, hybrid & semantic retrieval for RAG | — |

Each entry lives in its own folder and is directly linkable — locally via [`azure-ai-content-safety/`](./azure-ai-content-safety/index.html), or on the web at `/azure-ai-content-safety/`.

---

## How to view

**Locally** — just open the gallery in any browser:

```
azure-ai-services-presentations/index.html
```

Click a card to launch that deck. Each deck also opens on its own:

```
azure-ai-services-presentations/azure-ai-content-safety/index.html
```

**On the web (GitHub Pages)** — already live:

- Gallery: <https://kardelruveyda.github.io/azure-ai-services-presentations/>
- Each deck folder is directly linkable at its own path, e.g. `/azure-ai-content-safety/`.

Pages serves from the `main` branch root, so every push updates the site automatically.

---

## Structure

```
azure-ai-services-presentations/      ← repo root = GitHub Pages site root
├── index.html                        ← dark gallery landing page (links to each deck)
├── README.md                         ← this file
├── .gitignore                        ← ignores PDFs, presenter notes, temp files
└── azure-ai-content-safety/          ← deck 1 (independently linkable)
    ├── index.html                    ← the 15-slide presentation
    ├── README.md                     ← deck-level details
    ├── PRESENTER_NOTES.md            ← speaker script (git-ignored)
    └── *.pdf                         ← grounding source (git-ignored)
```

Every folder that contains an `index.html` is browsable at its own path — so adding a new deck is just adding a new folder and a card in the gallery.

---

## Design system

All decks share one dark, cinematic look:

| Token | Value |
|-------|-------|
| Background | `#0A1428` |
| Azure | `#0078D4` |
| Cyan | `#50E6FF` |
| Ink (text) | `#EAF2FB` |
| Muted | `#9DB2CC` |
| Glass surface | `rgba(255,255,255,0.06)` + backdrop-blur |
| Accent gradient | `linear-gradient(135deg,#0078D4,#50E6FF)` |

Self-contained (inline CSS/JS), honors `prefers-reduced-motion`, and uses the system font stack (Segoe UI).

---

## Adding a new presentation

1. Create a kebab-case folder (e.g. `azure-ai-foundry/`) — no spaces, no Turkish characters.
2. Drop in a self-contained `index.html` using the shared design tokens.
3. Add a `<a class="card live">` entry in the root `index.html` gallery and a row in the table above.
4. Use **relative paths** (`./...`) so links work both locally and on Pages.

---

## Notes

- `PRESENTER_NOTES.md` files and source `*.pdf` documents are **git-ignored** (see `.gitignore`).
- Decks are static HTML — safe to open offline and easy to hand off to customers.