> ## Documentation Index
> Fetch the complete documentation index at: https://veriqa.app/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Ready-made recipes

> Short routes through the documentation for common tasks, from sign-in to a web app to confirming an operation, plus detailed recipes for connecting a CMS and business systems.

A recipe answers the question "how do I do X" and takes you to the result step by step. Each step is
one sentence and a link to the page that covers it in detail, so a recipe contains almost no code.

The first step of every recipe is your own Veriqa server: in [Docker](/docs/quickstart/self-hosted) or
[as an OS service](/docs/quickstart/os-service). Veriqa Cloud is coming soon, and then you will not need
to deploy a server.

## Step-by-step recipes

| Recipe | What you get | What you need |
| - | - | - |
| [Passwordless sign-in for a Node.js, Python or Java web app](/docs/recipes/web-app-sign-in) | Users sign in with a QR code and no password, and sign up with the same action | A Veriqa server, a channel bot, access to the app's code |
| [Sign in with Telegram on a WordPress site](/docs/recipes/wordpress-telegram) | Telegram sign-in to WordPress with the stock plugin | A Veriqa server, a Telegram bot, WordPress administrator rights |
| [Moving off SMS codes](/docs/recipes/replace-sms) | A confirmation in a messenger instead of an SMS code, without losing users during the switch | A Veriqa server, the channels your audience uses |
| [Confirming a sensitive operation](/docs/recipes/confirm-operation) | A transfer, an email change or a data deletion runs only after it is confirmed in a messenger | A Veriqa server, access to your backend |
| [Team sign-in to GitLab, Grafana or Nextcloud](/docs/recipes/team-apps) | Employees sign in to business systems through Veriqa | A Veriqa server, administrator rights in the system |
| [A website form with a verified contact](/docs/recipes/lead-form) | A visitor confirms the form submission in a messenger, and the lead carries a verified contact | A Veriqa server, hosting for a server-side handler |
| [Sign-in on a Smart TV or a kiosk](/docs/recipes/smart-tv) | Sign-in with a QR code on a device without a keyboard | A Veriqa server, a backend for the app |

## Connecting a CMS

Detailed recipes for each engine: which plugin to install, how to configure it, which steps are
mandatory and what the resulting account looks like. What was verified on each engine is summarized
in [Veriqa in a CMS](/docs/integrations/overview).

* [WordPress](/docs/integrations/wordpress) — the stock `openid-connect-generic` plugin;
* [Drupal](/docs/integrations/drupal) — the `openid_connect` module;
* [1C-Bitrix](/docs/integrations/bitrix) — the stock `socialservices` framework;
* [TYPO3](/docs/integrations/typo3) — the `causal/oidc` extension;
* [Joomla](/docs/integrations/joomla) — the miniOrange OAuth Client;
* [Shopify, Wix and other SaaS builders](/docs/integrations/saas-builders) — sign-in through the
  platform's own SSO settings.

## Business systems and forms

* [Veriqa in business systems](/docs/integrations/apps) — GitLab, Keycloak, Grafana, Nextcloud,
  Discourse, Odoo and Moodle: what works, where the barrier is and how to clear it;
* [Confirmed form submission](/docs/integrations/confirmed-form) — a server-side handler for a form
  whose submission is confirmed in a messenger;
* [Testing the integration locally](/docs/integrations/local-testing) — how to stand up the setup on your
  own machine and which difficulties exist only locally.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.