[DRAFT] Chapter 3 technical IaaS baseline rewrite #3

Closed
karsten wants to merge 5 commits from chapter/3-technical-iaas-baseline into main
Owner

Current status

Initial technical text rewrite only. This is not ready for review or merge.

Still required:

  • full Chapter Work cross-chapter and reader-flow pass
  • relevant technical, terminology and public-safety controls
  • visual inventory, graphic creation and rendered-page inspection
  • release artefacts and final acceptance

Current text change

Rewrites Chapter 3 around projects, identity, compute, images, networking, storage, quotas, APIs, failure domains, automation and operational evidence. It explicitly defers cluster topology and workload rollout.

## Current status Initial technical text rewrite only. This is not ready for review or merge. Still required: - full Chapter Work cross-chapter and reader-flow pass - relevant technical, terminology and public-safety controls - visual inventory, graphic creation and rendered-page inspection - release artefacts and final acceptance ## Current text change Rewrites Chapter 3 around projects, identity, compute, images, networking, storage, quotas, APIs, failure domains, automation and operational evidence. It explicitly defers cluster topology and workload rollout.
karsten changed title from docs: rewrite Chapter 3 as technical IaaS baseline to [DRAFT] Chapter 3 technical IaaS baseline rewrite 2026-09-03 15:21:30 +00:00
Author
Owner

Closed as superseded by the completed Chapter 3 release merged through PR #4 into main (merge commit aab5f88ad5). The old draft branch is being removed as part of the requested Chapter 3 branch cleanup.

Closed as superseded by the completed Chapter 3 release merged through PR #4 into main (merge commit aab5f88ad500883274d03923505f02535b034dab). The old draft branch is being removed as part of the requested Chapter 3 branch cleanup.
karsten closed this pull request 2026-09-07 16:17:34 +00:00

Pull request closed

Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
giga/content!3
No description provided.