Move SPDX lines and add authorship (#21)

Signed-off-by: Alex Lovell-Troy <alovelltroy@lanl.gov>

Author: alexlovelltroy

.reuse/dep5

@@ -0,0 +1,16 @@
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Upstream-Name: Fabrica
+Upstream-Contact: OpenCHAMI <info@openchami.org>
+Source: https://github.com/openchami/fabrica
+
+Files: docs/_posts/*
+Copyright: 2025 OpenCHAMI Contributors
+License: MIT
+
+Files: docs/blog/*
+Copyright: 2025 OpenCHAMI Contributors
+License: MIT
+
+Files: docs/guides/* docs/reference/* docs/*.md
+Copyright: 2025 OpenCHAMI Contributors
+License: MIT

docs/_posts/2025-11-04-basic-crud.md

@@ -1,13 +1,8 @@
-<!--
-SPDX-FileCopyrightText: 2025 OpenCHAMI Contributors
-
-SPDX-License-Identifier: MIT
--->
-
 ---
 layout: post
 title: "Meet the Generated Client"
 description: "How the CLI and Go library help you use your API the same way every time."
+author: "Alex Lovell-Troy"
 ---
 
 APIs are easier to use when the client is predictable. You should not have to remember custom flags or one‑off scripts. Fabrica generates two clients that match your server: a CLI and a Go library. They share patterns and types, so your shell steps and your code read the same way.

docs/_posts/2025-11-04-cloud-events.md

@@ -1,13 +1,8 @@
-<!--
-SPDX-FileCopyrightText: 2025 OpenCHAMI Contributors
-
-SPDX-License-Identifier: MIT
--->
-
 ---
 layout: post
 title: "Events as a Simple State Machine"
 description: "How Fabrica’s event system lets you model and drive resource state changes."
+author: "Alex Lovell-Troy"
 ---
 
 Events let your API tell the world what changed. In Fabrica, that stream becomes more than a log. It is a simple way to model a resource’s state and move it forward. When a resource is created, updated, or deleted, the server publishes an event. When Status changes in a meaningful way, you can publish a condition change. Other parts of your system can subscribe and react.

docs/_posts/2025-11-04-pluggable-storage.md

@@ -1,13 +1,8 @@
-<!--
-SPDX-FileCopyrightText: 2025 OpenCHAMI Contributors
-
-SPDX-License-Identifier: MIT
--->
-
 ---
 layout: post
 title: "Pluggable storage in Fabrica: files to databases"
 description: "How the storage contract lets you swap file and database backends without changing your API, with a look at the FRU example."
+author: "Alex Lovell-Troy"
 ---
 
 Fabrica generates REST services from Kubernetes‑style resources. The shape is always the same: APIVersion, Kind, Metadata, Spec, and Status. Handlers, routes, models, and the client are generated from templates. What you store those resources in is up to you. The storage layer is pluggable, so you can start with files and move to a database later without rewriting your API.

docs/_posts/2025-11-04-rack-reconciliation.md

@@ -1,13 +1,8 @@
-<!--
-SPDX-FileCopyrightText: 2025 OpenCHAMI Contributors
-
-SPDX-License-Identifier: MIT
--->
-
 ---
 layout: post
 title: "Reconciliation: Let the System Do the Work"
 description: "A gentle look at controllers that react to change and keep resources in a good state."
+author: "Alex Lovell-Troy"
 ---
 
 Some jobs are better done by the system than by users clicking through steps. Reconciliation makes this possible. You declare what you want in Spec, and a controller reads that intent and works until the resource reaches a steady state. When things drift, the controller nudges them back.

docs/_posts/2025-11-04-spec-version-history.md

@@ -1,13 +1,8 @@
-<!--
-SPDX-FileCopyrightText: 2025 OpenCHAMI Contributors
-
-SPDX-License-Identifier: MIT
--->
-
 ---
 layout: post
 title: "Regenerate to Evolve: Adding Features After Release"
 description: "How updating Fabrica and regenerating code lets you grow existing APIs without rewrites."
+author: "Alex Lovell-Troy"
 ---
 
 APIs live for a long time. They grow as your product grows. The hard part is adding features without breaking what you already shipped. Fabrica is built for this kind of steady change. You keep your resource definitions as the source of truth. The generator keeps the rest in sync.

docs/_posts/2025-11-04-status-subresource.md

@@ -1,13 +1,8 @@
-<!--
-SPDX-FileCopyrightText: 2025 OpenCHAMI Contributors
-
-SPDX-License-Identifier: MIT
--->
-
 ---
 layout: post
 title: "When Standards Live in Code"
 description: "Why encoding REST rules in generators leads to steadier, more supportable APIs."
+author: "Alex Lovell-Troy"
 ---
 
 Many API teams say they follow REST, but each team writes it a little differently. Over time, small differences pile up. One service wraps list results in an object, another returns an array. One updates status together with spec, another splits them. These choices matter to users, and they matter even more when you have to support the API for years.

docs/_posts/2025-11-04-welcome-to-fabrica.md

@@ -1,13 +1,8 @@
-<!--
-SPDX-FileCopyrightText: 2025 OpenCHAMI Contributors
-
-SPDX-License-Identifier: MIT
--->
-
 ---
 layout: post
 title: "What the Generated Server Gives You"
 description: "A tour of the server you get from Fabrica and how it helps you ship stable APIs."
+author: "Alex Lovell-Troy"
 ---
 
 ## Context