docs: define CI/CD and Cloudflare architecture (#35) - #131
Merged
Conversation
Deploying lightning-it-documentation with
|
| Latest commit: |
95f34c1
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://1fac5de8.lightning-it-documentation.pages.dev |
| Branch Preview URL: | https://agent-issue-35-cicd-cloudfla.lightning-it-documentation.pages.dev |
Contributor
There was a problem hiding this comment.
Pull request overview
Defines the planning-only, implementation-ready CI/CD + Cloudflare Pages deployment architecture contract for publishing the Docusaurus site to https://docs.l-it.io, including trust boundaries, immutable artifact promotion, DNS/TLS expectations, acceptance, evidence, and rollback—intended as the handoff for #40 and gated by #38.
Changes:
- Adds a new architecture page describing the end-to-end deployment/promotion model, build contract, Cloudflare Pages contract, DNS/TLS contract, quality gates, acceptance, and rollback.
- Wires the new architecture page into the Docusaurus sidebar navigation.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| sidebars.ts | Adds the new CI/CD + Cloudflare architecture document to the Architecture sidebar section. |
| docs/architecture/cicd-cloudflare-deployment.md | Introduces the planning/architecture contract for immutable build + Cloudflare Pages deployment, acceptance, evidence, and rollback for docs.l-it.io. |
Comments suppressed due to low confidence (1)
docs/architecture/cicd-cloudflare-deployment.md:351
- For consistency with the rest of the repo documentation and with the earlier contract table, the command matrix should use
npm ci(without the extra--ignore-scripts=falseflag).
| builder | repository root | `npm ci --ignore-scripts=false` | lockfile | none | zero exit, no diff | discard workspace | install/lock digest |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Primary issue: #35
Changes
docsCNAME target, proxy/TTL, custom-domain sequence, Full (strict) TLS, minimum TLS 1.2, HTTPS/canonical-host, IPv4/IPv6, DNSSEC/CAA, and scoped rollback;Validation
git diff --checknpm run lintnpm run typechecknpm run test:contentnpm run buildincluding PagefindAll checks pass with Node 24.18.0.
Boundaries