wiki: auto-compile 2026-05-15 (1 log(s), 273 articles)

99 Daily/2026-05-15.md

@@ -77,3 +77,4 @@ tags: [daily]
 - 15:33 — session ended | `ai_leed`
 - 15:38 — session ended | `ai_leed`
 - 15:42 — session ended | `ai_leed`
+- 15:44 — session ended | `ai_leed`

wiki/_master-index.md

@@ -35,7 +35,7 @@ This 3-hop pattern works for hundreds of articles without vector search.
 | [[wiki/reports/_index\|reports/]] | Weekly and monthly summaries — generate: `uv run python scripts/report-generator.py --weekly` | 1 |
 | [[wiki/infrastructure/_index\|infrastructure/]] | Server inventory: all 10 SSH hosts — optical, optical-dev, optical-prod, baic, librechat, modocmms, box-cli, aimpress, pve | 12 |
 | [[wiki/testing/_index\|testing/]] | Web app testing: functional, performance, security, UI types; TDD/BDD/Agile methodologies; Selenium/Cypress/Playwright/JMeter/OWASP ZAP tools | 1 |
-| [[wiki/payloadcms/_index\|payloadcms/]] | Full Payload CMS reference — getting started, config, database (Postgres/MongoDB/SQLite), all 22 field types, access control, hooks, authentication (cookies, JWT, API keys, custom strategies, token data), admin UI, custom components, Lexical rich text, live preview, versions/drafts, Local/REST/GraphQL APIs, queries, plugins, jobs queue, upload, ecommerce, production deploy, TypeScript, migration guides, i18n, localization | 88 |
+| [[wiki/payloadcms/_index\|payloadcms/]] | Full Payload CMS reference — getting started, config, database (Postgres/MongoDB/SQLite), all 22 field types, access control, hooks, authentication (cookies, JWT, API keys, custom strategies, token data), admin UI, custom components, Lexical rich text, live preview, versions/drafts, Local/REST/GraphQL APIs, queries, plugins, jobs queue, upload, ecommerce, production deploy, TypeScript, migration guides, i18n, localization | 87 |
 
 | [[wiki/shared-patterns/_index\|shared-patterns/]] | Oliver Agency standard library patterns: httpx, structlog, pydantic-settings, alembic — reuse before writing from scratch | 4 |
 | [[wiki/mistakes/_index\|mistakes/]] | Anti-patterns extracted from sessions — per-stack running lists (fastapi, react, docker, postgres, general) — injected at session start | 5 |

wiki/payloadcms/getting-started.md

@@ -1,8 +1,10 @@
 ---
-tags: [payloadcms, tech-patterns]
-topic: payloadcms
+title: "PayloadCMS — Getting Started"
+aliases: [what-is-payload, payload-overview]
+tags: [payloadcms, tech-patterns, cms, nextjs, fullstack]
 sources: [getting-started__what-is-payload.md, getting-started__installation.md, getting-started__concepts.md]
 created: 2026-05-15
+updated: 2026-05-15
 ---
 
 # PayloadCMS — Getting Started
@@ -142,6 +144,32 @@ app/
 | `@payloadcms/richtext-lexical` | Rich text editor (optional) |
 | `@payloadcms/graphql` | GraphQL layer (bundled in `@payloadcms/next`) |
 
+## Use Cases
+
+| Use Case | Description | Quickstart |
+|----------|-------------|------------|
+| **Headless CMS** | Website content management with Live Preview, redirects, form builder, visual editing | `npx create-payload-app@latest -t website` |
+| **Enterprise Tool** | Internal apps — SSO auth, access control, admin UI, REST/GraphQL, migrations all built-in | `npx create-payload-app@latest -t blank` |
+| **Headless Commerce** | Full storefront without Shopify — products, catalogs, media, orders in one backend; offload only payments (Stripe) | `npx create-payload-app@latest -t blank` |
+| **Digital Asset Management** | API-first tagging/sorting/querying, folder organization, file versioning, bulk upload, media access control | `npx create-payload-app@latest -t blank` |
+
+## When to Use / Avoid
+
+### Use Payload when
+
+- Data ownership and privacy matter (no vendor lock-in)
+- Building a Next.js site that needs a CMS — install in existing repo
+- Custom business logic beyond a typical headless CMS
+- Need to reuse data outside of a SaaS API
+- Serverless deploy on Vercel is a requirement
+
+### Avoid Payload when
+
+- Project can be managed fully with code, no admin UI needed
+- Site fits within Webflow / Framer constraints
+- Already have a full DB and just need data visualization
+- Certain you'll never need code/data ownership
+
 ## Gotchas
 
 - All official Payload packages must use **matching version numbers** — mixing versions breaks things
@@ -152,8 +180,22 @@ app/
 - `sharp` is optional but required for image cropping, resizing, focal point selection
 - `graphql` package must be in your `package.json` explicitly if you use GraphQL queries
 
+## Key Takeaways
+
+- Payload is a **code-first Next.js fullstack framework** — not a SaaS; you own your data and schema
+- One config file (`payload.config.ts`) drives Admin Panel, DB schema, REST/GraphQL/Local APIs, auth, uploads simultaneously
+- Four distinct use cases: Headless CMS, Enterprise Tool, Headless Commerce, DAM — all from the same tool
+- **No click-ops** — schema is always version controlled; non-technical users operate via the generated Admin UI
+- MIT licensed, self-hostable on any Node.js host including Vercel serverless
+- Avoid if: no admin UI needed, project fits Webflow/Framer, or you already have a complete DB stack
+
 ## Related
 
-- [[wiki/payloadcms/configuration|Configuration]]
-- [[wiki/payloadcms/fields|Fields]]
+- [[wiki/payloadcms/configuration|Payload Config — Overview]]
+- [[wiki/payloadcms/concepts-overview|Core Concepts]]
+- [[wiki/payloadcms/installation|Installation]]
+- [[wiki/payloadcms/collection-config|Collection Config]]
 - [[wiki/payloadcms/hooks|Hooks]]
+- [[wiki/payloadcms/access-control|Access Control]]
+- [[wiki/payloadcms/ecommerce|Ecommerce]]
+- [[wiki/payloadcms/upload|Upload & Media]]