Articles

Purpose

This repository is designed to create a Web application that allows a user to create articles on any topic they wish and manage the publication of said articles when they are completed. The articles include a title, an introduction, a category, and the content of the full article. It also allows adding links, pictures, and other attachments. The author is responsible for managing their own articles. They can create, edit, and delete their articles as needed. An administrator oversees the platform to ensure content quality and compliance.

Repository structure

• .github/workflows — canonical CI/CD, lint, triage, sync, and release automation workflows.
• .github/hooks — local hook scripts (including pre-push gates).
• .github/instructions — coding and documentation instructions applied to contributors and agents.
• src — .NET implementation projects used by the standard toolchain.
• tests — architecture, domain, component, unit, and end-to-end test suites.
• docs — architecture, contribution guidance, and release-review history.
• Directory.Packages.props, global.json, and GitVersion.yml — shared dependency/version governance.

Documentation index

• Docs landing page — overview and documentation entry points.
• Architecture overview — repository layout and policy boundaries.
• Contributing guide — contribution workflow and validation expectations.
• Release review blog index — release-review post index.

Release review blogs

The release review posts in docs/blogs summarize the rollout history of workflow-standard and major changes by release.

Latest blogs (top 5, generated)

Date	Title	Tags
YYYY-MM-DD	Post title	tag1, tag2
2026-08-08	Add XML documentation to domain and host types	release,automation
2026-08-08	Add Playwright E2E coverage and app host improvements	release,automation
2026-08-07	Update project configuration, enhance components, and improve testing	release,automation
2026-08-06	Update project configuration, enhance UI components, and improve testing setup	release,automation

Quick start

For adopters (using this standard in another repo)

1. Review the standard and policy surface in .github/workflows, .github/hooks, and .github/instructions.
2. Copy the assets you want to adopt into your target repository.
3. Validate in CI and locally with the same gates this repo uses (workflows in .github/workflows, hook behavior in .github/hooks/pre-push).
4. Track updates through releases and release-review posts in docs/blogs.

For contributors (updating this repo)

1. Clone and restore:

   git clone https://github.com/mpaulosky/Articles.git
   cd Articles
   dotnet restore Articles.slnx

2. Run baseline validation:

   dotnet build Articles.slnx --configuration Release
   dotnet test Articles.slnx --nologo

3. Follow the full contribution workflow in docs/CONTRIBUTING.md.

Merged-PR release automation (concise)

The Squad Release workflow runs when a PR is merged to main (or by manual dispatch with a merged PR number).

Every merged PR to main is treated as release-eligible. The workflow runs one release/blog pass per PR (idempotency marker: Source PR: #<number> in release notes) and then:

• computes semver bump from PR labels, with idempotency checks to avoid duplicate releases,
• generates a release-review post and rebuilds docs/blogs/README.md,
• updates this README latest-blog block (` | Date | Title | Tags | |------|-------|------| | YYYY-MM-DD | Post title | tag1, tag2 | | 2026-08-08 | Add XML documentation to domain and host types | release,automation | | 2026-08-08 | Add Playwright E2E coverage and app host improvements | release,automation | | 2026-08-07 | Update project configuration, enhance components, and improve testing | release,automation | | 2026-08-06 | Update project configuration, enhance UI components, and improve testing setup | release,automation |

`)

from docs/blogs/README.md (top 5 rows),

• updates docs/index.html latest blog links from the same rows.