Add script to create a demo site for testing

[stevetemple]

Describe your changes

Add script to create a demo site for testing

Checklist before requesting a review

• I have performed a self-review of my code

[Copilot]

Pull request overview

Adds cross-platform scripts and documentation to scaffold a local Umbraco “demo” site that references the local Umbraco.Community.AzureSSO project, enabling easier manual testing of the SSO flow during development.

Changes:

• Added Bash and PowerShell scripts to scaffold a demo Umbraco site under demo/, reference the library project, inject placeholder AzureSSO config, and generate a combined local solution.
• Documented local development workflow in README.md.
• Updated .gitignore to exclude generated demo artifacts; minor .editorconfig comment cleanup.

Reviewed changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
src/.editorconfig	Updates header comment; (note: comment still conflicts with actual indentation setting).
scripts/install-demo-site.sh	New Bash script to scaffold a demo site, add project reference + config, and create a local solution.
scripts/install-demo-site.ps1	New PowerShell script to scaffold a demo site, add project reference + config, and create a local solution.
README.md	Adds “Local development” section describing how to run the scripts and use the generated site/solution.
.gitignore	Ignores generated demo/ folder and *.local.slnx; minor whitespace cleanup.

Comments suppressed due to low confidence (2)

scripts/install-demo-site.sh:186

• dotnet new sln is invoked without specifying the solution format, but subsequent commands assume a .slnx file (${SOLUTION_NAME}.slnx). Passing --format slnx makes the script deterministic across SDK versions and avoids accidentally generating an untracked ${SOLUTION_NAME}.sln.

echo "Creating unified solution..."
dotnet new sln -n "$SOLUTION_NAME" --force
dotnet sln "${SOLUTION_NAME}.slnx" add "$LIBRARY_PROJECT" --solution-folder "Library"

scripts/install-demo-site.ps1:138

• dotnet new sln is invoked without specifying the solution format, but the script then operates on $SolutionName.slnx. Passing --format slnx makes the script deterministic across SDK versions and avoids accidentally generating an untracked $SolutionName.sln.

Write-Host "Creating unified solution..." -ForegroundColor Green
dotnet new sln -n $SolutionName --force
dotnet sln "$SolutionName.slnx" add $LibraryProject --solution-folder "Library"

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.