Update tenant lifecycle tooling and retire docs/process
This commit is contained in:
@@ -79,7 +79,7 @@ related:
|
||||
- **Standalone Web**: optional `/help` public site generated from the same Markdown using Vite/React and server-side rendering for SEO.
|
||||
|
||||
## Governance & Backlog
|
||||
- Track work in `docs/process/todo/help.md` (create if needed) and link issues to article slugs.
|
||||
- Track work in bd issues and link them to article slugs.
|
||||
- Add CI checks:
|
||||
- Ensure every `.en.md` file has a matching `.de.md` file with equal `slug`/`version_introduced`.
|
||||
- Validate required front matter keys.
|
||||
|
||||
@@ -27,7 +27,7 @@ related:
|
||||
|
||||
## Optionaler Follow-up
|
||||
- Event als Vorlage duplizieren für zukünftige Produktionen.
|
||||
- Erkenntnisse oder Verbesserungswünsche in `docs/process/todo/` festhalten.
|
||||
- Erkenntnisse oder Verbesserungswünsche als bd-Issue festhalten.
|
||||
|
||||
### Weitere Hilfe
|
||||
Wende dich an success@fotospiel.app oder konsultiere die Legal-Pages-Ressource für Compliance-Formulierungen.
|
||||
|
||||
@@ -28,7 +28,7 @@ Direkt nach dem Zugriff auf einen neuen Kunden oder wenn neue Mitarbeitende eing
|
||||
## Best Practices
|
||||
- Mindestens zwei Owner-Rollen für Redundanz halten.
|
||||
- Branding oder Automationen zuerst im Staging-Kundenkonto testen.
|
||||
- Einladungen im Änderungslog (`docs/process/changes/`) dokumentieren.
|
||||
- Einladungen als bd-Issue dokumentieren.
|
||||
|
||||
### Weitere Hilfe
|
||||
Siehe `event-prep-checklist` für Event-Vorbereitung oder kontaktiere cx-team@fotospiel.app für Onboarding-Support.
|
||||
|
||||
@@ -27,7 +27,7 @@ related:
|
||||
|
||||
## Optional follow-up
|
||||
- Duplicate the event as a template for future productions.
|
||||
- Update `docs/process/todo/` with learnings or improvements for the product team.
|
||||
- Capture learnings or improvements as bd issues for the product team.
|
||||
|
||||
### Need more help?
|
||||
Reach success@fotospiel.app or consult the Legal Pages resource for compliance wording.
|
||||
|
||||
@@ -28,7 +28,7 @@ Right after receiving access to a new customer account or when onboarding new st
|
||||
## Best practices
|
||||
- Keep at least two Owner-level accounts for redundancy.
|
||||
- Use the staging customer account to test branding or automation before touching production.
|
||||
- Document invitations in the change log (`docs/process/changes/`).
|
||||
- Document invitations in a bd issue note.
|
||||
|
||||
### Need more help?
|
||||
See `event-prep-checklist` for event-level prep or contact cx-team@fotospiel.app for onboarding assistance.
|
||||
|
||||
Reference in New Issue
Block a user