Standardize website content layout

Build/Export-WebsiteArtifacts.ps1

@@ -238,7 +238,7 @@ $manifest = [ordered]@{
     artifacts = [ordered]@{
         api = 'WebsiteArtifacts/apidocs'
         docs = 'Website/content/project-docs'
-        examples = 'content/examples'
+        examples = 'Website/content/examples'
     }
 }
 

Website/README.md

@@ -0,0 +1,19 @@
+# GPOZaurr Website Content
+
+This folder contains curated source content that the Evotec website imports for the GPOZaurr project page.
+
+## Layout
+
+- `content/project-docs/` contains short project documentation pages shown under `/projects/gpozaurr/docs/`.
+- `content/examples/` contains curated website examples shown under `/projects/gpozaurr/examples/`.
+- `WebsiteArtifacts/` is generated by `Build/Export-WebsiteArtifacts.ps1` at the repository root and is intentionally ignored by Git.
+
+## Editing Rules
+
+- Keep this folder intentional and small.
+- Do not mirror the raw `Examples/` folder into the public website.
+- Add only examples that have a clear explanation, a small code sample, and a link back to the original source file.
+- Keep links rooted at `/projects/gpozaurr/` so the same content works on localhost, `evotec.xyz`, and `evotec.pl`.
+- Run `Build/Export-WebsiteArtifacts.ps1` when API artifacts need to be refreshed.
+
+The website pipeline prefers this `Website/content/...` layout over legacy root-level content folders.