Conversation
Blog posts, README, and docs/index.html updated for v1.2.0. Reviewed and approved by Aragorn.
github-actions
Bot
added
the
squad
🏗️ PR Added to Squad Triage QueueThis PR has been labeled with Next steps:
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #126 +/- ##
=======================================
Coverage 76.93% 76.93%
=======================================
Files 43 43
Lines 672 672
Branches 111 111
=======================================
Hits 517 517
Misses 105 105
Partials 50 50 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Pull request overview
Docs-only promotion dev → main to align public-facing documentation (GitHub Pages + README + dev blog) with the v1.2.0 state of the MyBlog solution.
Changes:
- Refreshes
docs/index.htmlcontent (overview, features, structure, release list, blog links). - Adds
docs/blog/landing page and Sprint/Release blog posts up through v1.2.0. - Rewrites
README.mdto reflect current architecture, tech stack, test projects, and release history; updates workflow message indentation fixes.
Reviewed changes
Copilot reviewed 9 out of 12 changed files in this pull request and generated 8 comments.
Show a summary per file
| File | Description |
|---|---|
| docs/index.html | Updates GitHub Pages landing page content, features, structure, and release/blog tables. |
| docs/blog/index.md | Adds blog landing page with “Latest Posts”, sprint grouping, and release timeline tables. |
| docs/blog/2026-04-24-release-v1-2-0.md | Adds v1.2.0 release write-up (Redis + L1/L2 caching). |
| docs/blog/2026-04-24-release-v1-1-0.md | Adds v1.1.0 release write-up (Tailwind theme system + testing reorg). |
| docs/blog/2026-04-20-sprint-3-e2e-tests-ci-hardening.md | Adds Sprint 3 write-up (E2E + CI hardening). |
| docs/blog/2026-04-20-sprint-2-cqrs-mediatr.md | Adds Sprint 2 write-up (CQRS/MediatR + validation behavior). |
| docs/blog/2026-04-20-release-v1-0-0.md | Adds v1.0.0 release write-up (SemVer + GitVersion automation). |
| docs/blog/2026-04-18-myblog-project-kickoff.md | Adds Sprint 1 kickoff write-up (initial architecture + foundations). |
| README.md | Rewrites README for v1.2.0 stack/structure/testing/release history. |
| .github/workflows/release-blog.yml | Adjusts YAML indentation inside `run: |
| .github/workflows/milestone-release-decision.yml | Adjusts YAML indentation inside `run: |
| .github/workflows/milestone-blog.yml | Adjusts YAML indentation inside `run: |
|
|
||
| When starting a new project, the first decisions matter. We chose: | ||
| - **Blazor Server** for rapid, interactive web development with C# | ||
| - **.NET 10** and **.NET Aspire 13.2.2** for modern, cloud-native capabilities |
There was a problem hiding this comment.
This post references .NET Aspire 13.2.2, but the repo's central package versions pin Aspire packages to 13.2.3 (Directory.Packages.props). Update the version number here to keep the historical write-up aligned with the actual repo state.
| - **.NET 10** and **.NET Aspire 13.2.2** for modern, cloud-native capabilities | |
| - **.NET 10** and **.NET Aspire 13.2.3** for modern, cloud-native capabilities |
| ### Instructions | ||
| - Write the post to \`docs/blog/${PUBLISH_DATE}-release-${SLUG}.md\` | ||
| - Update \`docs/blog/index.md\` to add the new post at the top of the Recent Posts table | ||
| - Follow existing post style (see \`docs/blog/2026-04-04-release-v0-7-0.md\`) |
There was a problem hiding this comment.
The blog brief instructions reference docs/blog/2026-04-04-release-v0-7-0.md, but that file does not exist in docs/blog/. Update the reference to an existing example post (or remove it) to avoid sending contributors to a dead link.
| - Follow existing post style (see \`docs/blog/2026-04-04-release-v0-7-0.md\`) | |
| - Follow the existing post style used in \`docs/blog/\` |
| ### Instructions | ||
| - Write the post to \`docs/blog/${PUBLISH_DATE}-${SLUG}.md\` | ||
| - Update \`docs/blog/index.md\` to add the new post at the top of the Recent Posts table | ||
| - Follow existing post style (see \`docs/blog/2026-04-04-release-v0-7-0.md\`) |
There was a problem hiding this comment.
The blog brief instructions reference docs/blog/2026-04-04-release-v0-7-0.md, but that file does not exist in docs/blog/. Update the reference to an existing example post (or remove it) to avoid sending contributors to a dead link.
| - Follow existing post style (see \`docs/blog/2026-04-04-release-v0-7-0.md\`) | |
| - Follow the existing style used by posts in \`docs/blog/\` |
| | Date | Title | Tags | | ||
| |------|-------|------| | ||
| | 2026-04-24 | [Release: v1.2.0 — Redis Caching and L1/L2 Cache Strategy](./2026-04-24-release-v1-2-0.md) | release, v1.2.0, redis, caching, aspire, sprint-5 | | ||
| | 2026-04-24 | [Release: v1.1.0 — Blazor Theme System with TailwindCSS v4](./2026-04-24-release-v1-1-0.md) | release, v1.1.0, blazor, tailwind, theme, testing, sprint-4 | | ||
| | 2026-04-20 | [Release: v1.0.0 — Semantic Versioning and Production Readiness](./2026-04-20-release-v1-0-0.md) | release, semver, ci, devops | |
There was a problem hiding this comment.
docs/blog/index.md's Latest Posts table is malformed (lines start with ||) so the blog-readme-sync.yml regex (| Date | Title | Tags |) will not match and README sync will be skipped. Change the table header/separator/rows to use single | and ensure the header line is exactly | Date | Title | Tags |.
| | Release | Date | Focus | | ||
| |---------|------|-------| | ||
| | [v1.0.0](./2026-04-20-release-v1-0-0.md) | 2026-04-20 | Semantic versioning, production readiness | | ||
| | [v1.1.0](./2026-04-24-release-v1-1-0.md) | 2026-04-24 | Blazor theme system, test reorganization | | ||
| | [v1.2.0](./2026-04-24-release-v1-2-0.md) | 2026-04-24 | Redis caching, distributed cache strategy | |
There was a problem hiding this comment.
The Release Timeline table uses || at the start of each row, which renders as an extra empty column and makes the table harder to read/maintain. Use standard Markdown table syntax with single leading/trailing | characters.
|
|
||
| <pre><code>cd src/Web | ||
| npm run css:watch | ||
| <pre><code>npm run css:watch |
There was a problem hiding this comment.
npm run css:watch does not exist in the root package.json (scripts are tw:watch / tw:build). Update the command here to match the actual Tailwind watch script so the instructions work when followed.
| <pre><code>npm run css:watch | |
| <pre><code>npm run tw:watch |
| - **Blazor Server (Interactive Server Rendering)** — Dynamic UI | ||
| - **xUnit** — Test framework | ||
| - **FluentAssertions** — Assertion library | ||
| - **.NET Aspire 13.2.2** — Service orchestration, MongoDB + Redis resources, health checks |
There was a problem hiding this comment.
README lists .NET Aspire 13.2.2, but Directory.Packages.props pins Aspire packages to 13.2.3. Please update the documented Aspire version to match the versions actually used by the solution.
| - **.NET Aspire 13.2.2** — Service orchestration, MongoDB + Redis resources, health checks | |
| - **.NET Aspire 13.2.3** — Service orchestration, MongoDB + Redis resources, health checks |
| - [SECURITY.md](docs/SECURITY.md) — Security guidelines | ||
| - [CODE_OF_CONDUCT.md](docs/CODE_OF_CONDUCT.md) — Community standards | ||
| - [REFERENCES.md](docs/REFERENCES.md) — NuGet and npm package references | ||
|
|
There was a problem hiding this comment.
The repo has an active blog-readme-sync.yml workflow that updates the README by replacing the section between <!-- BLOG_START --> and <!-- BLOG_END -->, but this README currently contains no such markers, so the sync job will never apply updates. Add a Dev Blog section with those markers (or update/retire the workflow) so the automation works as intended.
| ## Dev Blog | |
| <!-- BLOG_START --> | |
| - Dev blog posts will be synced here automatically. | |
| <!-- BLOG_END --> |
🔱 Aragorn — Lead Developer ReviewCI: ✅ All checks passed | Copilot review: ✅ Read & verified ❌ CHANGES REQUIRED — 3 blocking issues1. Wrong npm script —
-<pre><code>npm run css:watch
+<pre><code>npm run tw:watch2. Missing blog-sync markers —
Add a Dev Blog section with the markers: ## Dev Blog
| Date | Title | Tags |
|------|-------|------|3. Aspire version mismatch — Both say .NET Aspire 13.2.2;
|
| Check | Result |
|---|---|
| All CI checks | ✅ PASS |
No .squad/ file leakage |
✅ |
| Blog post YAML front matter | ✅ |
| Blog post 4-section structure | ✅ |
docs/index.html release table (v1.0.0–v1.2.0) |
✅ |
npm install path corrected to repo root |
✅ |
| Workflow YAML heredoc indentation fix | ✅ |
docs/blog/index.md table syntax (Copilot || concern was false-positive) |
✅ |
| README tech stack / project structure | ✅ (pending Aspire version fix) |
Fix the 3 items above and this is good to merge. — Aragorn
Fixes 3 review blockers identified in PR #126 review: - docs/index.html: npm run css:watch → npm run tw:watch (matches root package.json) - README.md + kickoff blog post: Aspire 13.2.2 → 13.2.3 (matches Directory.Packages.props) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
🔱 Aragorn — Re-review after PR #127 fixes ✅ APPROVEDAll 3 blockers are resolved (verified in PR #127, now merged into
CI: ✅ All checks pass — merge state: CLEAN Merging to |
Summary
Promotes
dev→mainwith the Sprint 5 post-release documentation update.Changes included
docs/blog/— 7 new blog posts covering Sprint 1 through v1.2.0README.md— full rewrite for v1.2.0 (correct tech stack, project structure, release history)docs/index.html— de-staled GitHub Pages site (correct releases, architecture, blog links)Notes
squad/docs-sprint5-post-release(PR docs: post-release documentation update for v1.2.0 #125).main; this merge brings the divergent histories together.Closes #126 (if applicable)