Table of Contents

Contributing overview

Reignite is a .NET-first portfolio. The workspace standard is C# / .NET with SQL Server, hosted on Azure App Service. Follow the owning repository's constraints when a repository differs; do not introduce a second runtime for convenience.

Stack standards

Layer Standard
Backend services C# / .NET 8 / ASP.NET Core
Data SQL Server, EF Core
Hosting Azure App Service on Linux
Client tooling TypeScript/Node only where the repository already uses it (for example, the website's build and Playwright tests)
Documentation .NET 10 LTS host / DocFX / Markdown / Mermaid

The website pins the .NET 8 SDK in global.json (8.0.424). Do not remove that pin to build with a newer SDK; the .NET 10 Razor source generator has a known issue with consecutive <link asp-append-version> elements in a @section Head block, which ships unresolved ~/ hrefs.

The docs repo targets .NET 10 LTS (global.json selects 10.0.400) because Azure App Service no longer offers .NET 8 to new apps. DocFX ships a .NET 10 build, so the docs build needs only the .NET 10 SDK.

Repository map

The generated repository map lists every repository, its responsibility, its stack and its status. Start there when you need to know where a service lives.

Branch and merge discipline

  • Branch by the kind of work: feat/<id>, fix/<descriptor>, chore/<descriptor>, audit/<descriptor>.
  • Feature branches are based on dev; dev and main only ever merge. Do not hand-promote dev to main outside the project's sanctioned pipeline.
  • Commit early and often. A committed change survives the worktree-repair sweep; an uncommitted one does not.
  • Do not commit generated build output, bin/, obj/, _site/ or publish/.

Before you open a pull request

  1. Build the repository.
  2. Run its tests.
  3. If the change affects the architecture, update architecture/model.yaml in the docs repository and regenerate the diagrams.
  4. Confirm the docs build (./scripts/build.ps1 in the docs repository) succeeds.

Documentation rule

The architecture pages are generated. Do not hand-edit a file under docs/architecture/generated/. Edit the model and regenerate; the generator validates ids, relationship endpoints, repositories and flow participants before writing anything.

Where to go next