feat: add community publishing and news syndication

README.md

@@ -1,8 +1,8 @@
 # SHD.build
 
-A SvelteKit community application for *The Division Resurgence*. SHD.build
-combines a public game database, loadout builder, shared builds, guides,
-account management, and the ISAC data-management console.
+A SvelteKit community application for _The Division Resurgence_. SHD.build
+combines a public game database, loadout builder, shared builds, guides, account
+management, and the ISAC data-management console.
 
 See `docs/architecture.md` for the implementation model.
 
@@ -17,13 +17,12 @@ Create or update the local database:
 npm run db:migrate
 ```
 
-The default file is `data/shd-build.db`. Copy `.env.example` to `.env` and
-set a different location if needed.
+The default file is `data/shd-build.db`. Copy `.env.example` to `.env` and set a
+different location if needed.
 
 Store custom avatars as metadata-free 256 × 256 WebP files. Set
-`TDR_AVATAR_STORAGE_PATH` to a persistent, writable directory in production;
-it defaults to `data/avatars`. The same configuration works on Windows and
-Linux.
+`TDR_AVATAR_STORAGE_PATH` to a persistent, writable directory in production; it
+defaults to `data/avatars`. The same configuration works on Windows and Linux.
 
 Seed the initial local accounts once:
 
@@ -31,9 +30,9 @@ Seed the initial local accounts once:
 npm run db:seed-users
 ```
 
-The seed creates administrator `Aewyn` and standard user `Quartermaster`.
-It generates and displays strong temporary passwords once, then stores only
-salted Argon2id hashes.
+The seed creates administrator `Aewyn` and standard user `Quartermaster`. It
+generates and displays strong temporary passwords once, then stores only salted
+Argon2id hashes.
 
 ## Develop
 
@@ -74,9 +73,9 @@ game-data icons under `/app/data` on a persistent volume. Inject runtime secrets
 when the container starts; keep them out of the image.
 
 [docs/DEPLOYMENT.md](docs/DEPLOYMENT.md) documents the staging Compose topology
-and Gitea Actions deployment. A push to `main` validates the application,
-builds the candidate image while staging stays online, stops the application
-and scheduler for the database backup and migration, then starts the release.
+and Gitea Actions deployment. A push to `main` validates the application, builds
+the candidate image while staging stays online, stops the application and
+scheduler for the database backup and migration, then starts the release.
 
 ## Passwordless authentication
 
@@ -136,7 +135,8 @@ npm run build
 
 Preview the production build with `npm run preview`.
 
-> Deployments may require an [adapter](https://svelte.dev/docs/kit/adapters) for the target environment.
+> Deployments may require an [adapter](https://svelte.dev/docs/kit/adapters) for
+> the target environment.
 
 The shared visual language and dashboard conventions are documented in
 [docs/DESIGN_SYSTEM.md](docs/DESIGN_SYSTEM.md).