We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Document env file update behavior for setup scripts Both scripts use the same priority order (.env.local, .env.development, .env) and discover sibling projects. The Zitadel script also writes Docker Compose variables to the root .env. Clarified that --update-env on the OpenFGA script targets the same files, not just .env.local. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Simplify infrastructure setup using automated scripts Replace manual 5-step process with the two setup scripts that automate everything: setup-zitadel.sh (--docker-init --update-env) handles Docker startup, project/roles/OIDC app creation, and env file updates; setup-openfga.sh (--update-env) handles store and model setup. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Add full infrastructure setup steps to Getting Started Document the multi-step process: start containers, configure Zitadel project, run OpenFGA setup script, update .env.local, and restart containers to pick up the new environment variables. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Fix Getting Started to clarify API vs frontend Docker stacks The API repo's docker-compose.yml only provides infrastructure services (Zitadel, OpenFGA, PostgreSQL, etc.) — PHP and Composer are still required for the API itself. Only the frontend repo has a full-stack Docker setup that doesn't require local PHP. Restructured the page to make this distinction clear. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Remove duplicate H1 headers from all wiki pages GitHub wiki already displays the page title from the filename, so H1 headers that duplicate the title create redundant "Title Title" display. Removed from all 17 content pages. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Add navigation footers to all wiki pages Each page now has a footer with its section name, prev/next links within the section, and a Home link. Sections: For Users, For Webmasters, For Liturgists, For Developers (3 pages), For Contributors (3 pages), Testing (3 pages), Authentication & RBAC (5 pages). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Reorganize wiki into user, developer, and contributor sections Restructure the wiki around three audiences: users (calendar subscriptions, component libraries), developers (API reference, examples), and contributors (setup guide, source data, testing, auth infrastructure). Home page becomes a landing page routing visitors to the right section. API reference content extracted to its own page. New Getting Started and Using the API pages added. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>