docs(agent): refresh architecture/CLAUDE.md docs for Payload CMS (MITHOME-95)
CI Pipeline with Test Management / 🧪 Run Tests & Generate Reports (push) Canceled after 0s
Test Reporting & Gherkin Analysis / 🧪 Run Tests & Generate Reports (push) Canceled after 0s
CI Pipeline with Test Management / 🐳 Docker Integration Tests (push) Canceled after 0s
CI Pipeline with Test Management / 🏗️ Build Docker Image (push) Canceled after 0s
CI Pipeline with Test Management / 📊 Generate Test Summary (push) Canceled after 0s
Test Reporting & Gherkin Analysis / 📊 Analyze Test Coverage (push) Canceled after 0s
Test Reporting & Gherkin Analysis / 🔄 Sync with Linear (push) Canceled after 0s
Test Reporting & Gherkin Analysis / ⚡ Performance Monitoring (push) Canceled after 0s

The Content layer description across the AI-agent steering docs still
described the pre-migration JSON system as the live, current mechanism
— rule #1 in CLAUDE.md and the Content row in architecture.md
explicitly told future work (and future agent sessions) to edit
proto/src/content/pages/*.json directly, which the live site hasn't
read since MITHOME-91.

Rewrote, per the ticket's named targets:
- .agent/steering/architecture.md: system overview, the Content layer
  table row, rule #1, and the Content Management code example now
  describe Payload Globals/Collections + the payload-content.ts Local
  API adapter, with /admin as the editing surface.
- CLAUDE.md: Stack line now names Payload CMS, rule #1 rewritten the
  same way, and the project-structure tree gets the (frontend)/(payload)
  route groups, globals/, collections/, and payload.config.ts that were
  entirely missing from it.

Also fixed directly-adjacent staleness found while doing this pass —
same "how is content edited" documentation debt, just not literally
named in the ticket:
- .agent/AGENTS.md: same project-structure tree gap as CLAUDE.md.
- .agent/workflows/new-feature.md: step 3 told contributors to edit
  the JSON file directly; now points at the Payload config + admin.
- .agent/workflows/review.md: the example "flag hardcoded text" review
  comment suggested moving it into the JSON file.
- .agent/steering/development-rules.md: the TRADEOFF code example
  literally used "JSON content management vs CMS" as a live open
  decision — that decision is resolved, updated the example to match.
- README.md: the entire "Tartalomkezelés" section and a "CMS
  Publikálás gomb" paragraph described the retired content-editor.js
  workflow (git-push-based publish, JSON directory tour) as current;
  also dropped a dead link to docs/felhasznaloi-utmutato.md, deleted
  in MITHOME-93.

Doc-only change, no proto/ source touched — no gate to run beyond a
sanity re-read of each edited file.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
Do Siki
2026-09-13 12:33:33 +02:00
co-authored by Claude Sonnet 5
parent 3573d2accb
commit 758ee2cfed
7 changed files with 62 additions and 36 deletions
+13 -7
View File
@@ -10,14 +10,14 @@
- **Projekt**: mozdIT Bt. weboldal (websitedev)
- **Plane workspace**: `developments``pm.llmdev.mozdit.hu`
- **Stack**: Next.js 15, React 19, TypeScript, Tailwind CSS 4, MongoDB, Winston
- **Stack**: Next.js 15, React 19, TypeScript, Tailwind CSS 4, Payload CMS (self-hosted, `/admin`), MongoDB, Winston
- **Fő könyvtár**: `proto/`**minden parancsot innen futtatunk**
---
## Gyors referencia — Alapszabályok
1. **Szöveg sosem kerülhet közvetlenül komponensbe**`proto/src/content/pages/*.json`
1. **Szöveg sosem kerülhet közvetlenül komponensbe**Payload CMS Global/Collection mező (admin: `/admin`), a frontend `proto/src/lib/payload-content.ts`-en át olvassa. (`proto/src/content/pages/*.json` már csak a migrációs seed-script forrása + teszt-fixture, élő oldal nem használja — MITHOME-91/93/96.)
2. **Feladatok**: `TODO.md` (Plane tükörképe), szinkron: `node plane-sync.js`
3. **Tesztek**: minden feature-höz kötelező; commit előtt `npm test` zöld
4. **Commit**: Conventional Commits (`feat:`, `fix:`, `docs:`, `chore:`)
@@ -47,12 +47,17 @@ node plane-sync.js # Plane szinkronizáció
websitedev/
├── proto/ # Fő Next.js alkalmazás
│ └── src/
│ ├── app/ # App Router: oldalak és API route-ok
│ ├── app/
│ │ ├── (frontend)/ # Publikus oldalak: [locale]/[slug] catch-all
│ │ └── (payload)/ # Payload admin (/admin) + REST/GraphQL API
│ ├── components/ # React komponensek (PascalCase.tsx)
│ ├── content/ # JSON tartalom-kezelő rendszer
├── common.json # Közös szövegek
│ └── pages/ # Oldal-specifikus JSONok
│ ├── lib/ # MongoDB, Logger, Site Config
│ ├── globals/ # Payload Globals (Home, About, Services, Contact, Common)
│ ├── collections/ # Payload Collections (LegalPages, Partners, Media, ContactSubmissions, Users)
├── payload.config.ts # Payload CMS konfiguráció
│ ├── content/ # RÉGI JSON rendszer — csak migrációs seed + teszt-fixture (MITHOME-91/93/96)
│ │ ├── common.json
│ │ └── pages/
│ ├── lib/ # payload-content.ts (Local API adapter), MongoDB health-check, Logger
│ ├── config/ # Statikus site konfiguráció
│ └── types/ # TypeScript típusok
├── docs/ # Projekt dokumentáció (Magyar)
@@ -77,6 +82,7 @@ Szükséges változók (`.env` és `proto/.env.local`):
- `NEXT_PUBLIC_CONTACT_EMAIL` — Kapcsolati email cím
- `PLANE_API_KEY` — Plane szinkronizációhoz (a `.mcp.json`-ban is lehet)
- `PAYLOAD_SECRET` — Payload CMS JWT/session aláíráshoz (MITHOME-86); környezetenként egyedi, erős érték
- `ADMIN_EMAIL` / `ADMIN_PASSWORD` — staging/production: `deploy.sh` ezekkel hoz létre egy ismert admin usert egy vadonatúj adatbázison (MITHOME-97 follow-up), csak akkor, ha a `users` collection még üres
---