Skip to content

Commit b843a6e

Browse files
csharpfritzCopilot
andcommitted
chore: commit squad state files (decisions inbox, agent history)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
1 parent 98ff298 commit b843a6e

3 files changed

Lines changed: 24 additions & 0 deletions

File tree

.squad/agents/jubilee/history.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -362,3 +362,5 @@
362362

363363

364364
Team update (2026-03-22): AfterDepartmentPortal Blazor SSR scaffold completed and integrated into solution. 31 files, 7 pages, 12 shared components, 6 models. Project builds clean. Decisions merged to shared decisions.md. decided by Jubilee
365+
366+
**Runnable demo (2026-03-22):** Made AfterDepartmentPortal fully runnable. App.razor now uses Bootstrap 5.3.3 CDN + Bootstrap Icons CDN instead of missing local CSS. Site.css copied from DepartmentPortal source. Home.razor at /home provides navigation cards to all sections. Fixed SectionPanel duplicate CssClass parameter bug (`new` keyword shadowed base class `[Parameter]`, causing AmbiguousMatchException). Dashboard already owns `@page "/"` so Home lives at `/home`. All routes verified returning 200.
Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
### 2026-03-22T16-22-17Z: User directive
2+
**By:** Jeffrey T. Fritz (via Copilot)
3+
**What:** Devise a strategy to extract CSS and JS content from NuGet packages that use the old ASP.NET Web Forms BundleConfig pattern, and place them in wwwroot/ during migration. This should handle the gap where Web Forms apps reference static assets via NuGet packages (e.g., jQuery, Bootstrap) that get unpacked into Content/Scripts folders, and those references disappear when migrating to Blazor.
4+
**Why:** User request captured for team memory. This is a real migration gap discovered during the DepartmentPortal migration: the CSS was identical but nobody thought to copy it because the delivery mechanism (NuGet + BundleConfig) is completely different in Blazor (wwwroot + CDN/libman).
Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
# Decision: AfterDepartmentPortal Runnable Demo Setup
2+
3+
**Date:** 2026-03-23
4+
**Author:** Jubilee (Sample Writer)
5+
**Status:** Implemented
6+
7+
## Context
8+
AfterDepartmentPortal built clean but couldn't render — missing CSS files and no home page.
9+
10+
## Decisions
11+
12+
1. **Bootstrap via CDN** — Used Bootstrap 5.3.3 and Bootstrap Icons from jsdelivr CDN instead of bundling local copies. Keeps the sample lightweight and avoids checking large vendor files into the repo.
13+
14+
2. **Home page at /home, not /** — Dashboard.razor already claimed `@page "/"`. Rather than disrupting the existing route, the new Home.razor welcome page lives at `/home`. The Dashboard *is* the landing page.
15+
16+
3. **SectionPanel CssClass fix** — Removed `new CssClass` property that shadowed the base class `[Parameter]`. Blazor parameters are case-insensitive and must be unique across the inheritance chain. Used `OnInitialized()` to set the default instead.
17+
18+
4. **Site.css copied from DepartmentPortal** — Preserves the same CSS classes used by the before/after migration pair, ensuring visual consistency.

0 commit comments

Comments
 (0)