Frank
c37ad6e870
An index is the skim layer: its entries decide whether a reader opens the page, so an entry that runs 250 characters is a paragraph wearing a bullet. Four entries in `tools/index.md` (`dotfiles-deploy`, `packages`, `pcie-probe`, `remote-job`) now say what the page is for in one line and let the page carry the detail — which is the whole argument for progressive disclosure having an index at all. `engineering/infra/index.md` pointed at `../sdlc.md` with no description at all; it now carries the one from that page's frontmatter, like its four siblings. Refs #64
16 lines
615 B
Markdown
16 lines
615 B
Markdown
# Infrastructure and Cloud
|
|
|
|
Current (2025/2026) best practices for infrastructure as code, containers, orchestration, and cloud providers.
|
|
|
|
## Topics
|
|
|
|
* [Terraform and OpenTofu](terraform.md) - IaC modules, state, backends, and orchestration.
|
|
* [Docker and Podman](containers.md) - BuildKit, multi-stage builds, rootless, and pods.
|
|
* [Kubernetes](kubernetes.md) - Helm, k3s, k0s, and Talos.
|
|
* [Cloud Providers](cloud.md) - AWS, DigitalOcean, and Hetzner.
|
|
|
|
## See Also
|
|
|
|
* [Engineering](../index.md) - The parent area.
|
|
* [SDLC and Tooling](../sdlc.md) - git, CI/CD, testing, review, versioning, and dev environments.
|