selise-blocks

Plugin selise-blocks from marketplace selise-blocks in SELISEdigitalplatforms/blocks-skills. Commands read from the repo's manifest — 5 days ago.

Skills (25)

• blocks-bootstrap

  Get a user from any starting state to a working SELISE Blocks setup — CLI installed, logged in, project selected — using the `blocks` CLI, never raw fetch/curl. Detects state from `blocks auth status --json` and `blocks doctor --json`, then routes to a flow: select or create a project, inventory a p

• blocks-captcha

  Configure the login captcha of a SELISE Blocks project through the blocks CLI ('captcha list/get/save/enable/disable/delete'): register a reCAPTCHA or hCaptcha site key and secret, switch it on or off, see which configuration blocks-iam actually enforces at login, and retire one. CLI-only, project-s

• blocks-data-gateway-configuration

  Configure a SELISE Blocks project's data model via the blocks CLI — never raw fetch/curl against api.seliseblocks.com. Covers data-source config (data config get/create/update), schema authoring and push (data schema list/pull/push, plus granular get/fields/info/indexes commands), data-access polici

• blocks-data-gateway-crud

  Implement create/read/update/delete against a SELISE Blocks project's runtime Data Gateway using the @seliseblocks/client SDK. Use data.collection(schemaName) for straightforward per-item CRUD, data.graphql() for joins or custom query shapes, and data.schemas.*/data.validations.* for schema/validati

• blocks-data-storage

  Build file and document-management features on SELISE Blocks Data: upload/download, directory trees, cursor-paginated browsing and search, file versions, rename/move/copy, soft delete/trash/restore, sharing, access policies, and inheritance. Use for attachments, file browsers, folders, shared files,

• blocks-frontend-local-https

  Run a scaffolded (`blocks new web`) Blocks app locally over HTTPS on its real project domain — required for hosted IAM login, since plain HTTP or localhost never gets the session cookie. The scaffold already automates cert generation (npm run cert, no OpenSSL needed) and HTTPS serving via vite.confi

• blocks-functions

  Serverless Node functions on Blocks Logic: write the handler (index.js + package.json), save/test/deploy with `blocks logic function *`, then call it from app code with the SDK's `blocksClient.logic.functions.call()/invoke()` or from a workflow `function` step. Covers triggers (HTTP methods, Public

• blocks-iam-access-control

  Work with SELISE Blocks RBAC (roles & permissions) via `blocks iam roles/permissions *` (CLI, project-scoped) or `blocksClient.iam.*` (SDK), never raw fetch/curl. Two facets: read-only feature-gating by the current user's own roles/permissions (common, safe), and creating/editing role and permission

• blocks-iam-account

  Signed-in (or partially-signed-in) user's own SELISE Blocks IAM account actions via @seliseblocks/client — never raw fetch/curl. Covers activation, forgot/reset/change password, logout(-all), profile bootstrap (iam.me/updateMe), self-service MFA, signup, and login-options discovery. Use for activati

• blocks-iam-mfa

  Self-service MFA for the signed-in user's own account — TOTP enroll/verify, OTP generate/resend/verify, method switch, disable, backup codes — via `blocksClient.mfa.*` or the project-scoped `blocks mfa *` CLI, plus tenant-wide MFA policy admin (`mfa.saveConfig` / `blocks mfa config get/save`). Use f

• blocks-iam-organizations

  Manage Blocks organizations and signup policy through the SDK (`iam.organizations`, `iam.signupSettings`, `auth.switchOrganization`) or project-scoped CLI (`blocks iam organizations *`, `iam signup-settings *`). Use for org switchers, active-org switching, multi-org settings, organization CRUD, and

• blocks-iam-sso-oidc-configuration

  Enable/configure SSO for a Blocks project — register an OIDC client and identity provider so end users can log into the app via hosted login. Use for 'enable SSO', 'set up an OIDC identity provider', 'configure single sign-on', 'add a login provider'. CLI-driven by default (`blocks auth oidc-clients

• blocks-iam-sso-oidc-implementation

  Extend or debug the hosted SSO/OIDC login flow `blocks new web` scaffolds into every Blocks app: redirectToProvider → `/login/callback` → session, through the single `blocksClient`. Covers `AuthProvider` status/claims, `RequireAuth`/`RedirectIfAuthenticated` guards, and token refresh. Use for a logi

• blocks-iam-users

  Manage OTHER users' IAM records via `blocksClient.iam.users.*` (never raw fetch/curl), or the equivalent project-scoped `blocks iam users *` / `blocks iam email available` CLI. Covers reads (`get`, `list`, `emailAvailable`, `exists`) and admin mutations (`create`, `update`, `activate`, `deactivate`,

• blocks-localization-configuration

  Configure app translations (i18n) for a SELISE Blocks project through the `blocks` CLI — never raw fetch/curl. Covers authoring local i18n JSON dictionaries, validate/push/pull with the Localization service, managing languages and modules directly, glossary terms, AI translation suggestions, and the

• blocks-localization-implementation

  Consume SELISE Blocks localization at runtime in a scaffolded frontend, entirely through the `@seliseblocks/client` SDK's `localization` namespace — never raw fetch/curl. Use for making a Blocks web app multilingual on the client: language/module discovery, loading dictionaries, the built-in `t()` l

• blocks-mail

  Send transactional email via the SDK's `blocksClient.mail.send()`/`sendToAny()`, or administer mail via the project-scoped `blocks mail config|template|mailbox *` CLI — server config, template CRUD/clone, mailbox reads, none of which have an SDK equivalent. CLI also exposes `mail send`/`sendtoany` a

• blocks-notification

  Manage SELISE Blocks notification-channel configuration via `blocks notification *` — no SDK path exists (`@seliseblocks/client` has no `notification` namespace, only the unrelated real-time `notifier` surface). Covers `notification list`/`get` (read configs) and `notification save`/`delete` (projec

• blocks-notifier

  Push real-time/offline notifications and manage a signed-in user's own notification inbox, via both the SDK (`blocksClient.notifier.*`) and the CLI (`blocks notifier notify|list|unread|mark-read|mark-all-read`). Distinct from the sibling blocks-notification skill, which configures tenant notificatio

• blocks-proxy

  Call a third-party API from app code without shipping its URL or keys: configure a Blocks Logic proxy with `blocks logic proxy *` (upstream, declared routes, injected headers with `{{$VAR.name}}` secrets, who-can-call access, timeout/retry/circuit breaker, rate limit, OpenAPI import), then call it w

• blocks-release-deployment

  Trigger and inspect SELISE Blocks Release builds/deploys entirely through `blocks release *` — never raw fetch/curl; there is no SDK path. Covers `deploy` (re-deploy), `setup` (first deploy), `status`/`logs` (by build id), `repos list`/`builds list` (inventory), `secrets sync` (env vars from a doten

• blocks-secrets

  Manage a SELISE Blocks project's secret store through the blocks CLI ('secrets list/get/set/set-many/update/rotate/lock/unlock/delete/restore/access/audit'): create named secrets from a file, env var or dotenv, rotate, lock, soft-delete/restore, set who may read them, and read the audit trail. The C

• blocks-storage-configuration

  Configure which storage provider (Azure Blob, S3-compatible object storage, or local/SFTP storage) backs a SELISE Blocks project's file object tree: named configurations with host, port, credentials, region/endpoint or connection string, and strategy, via the blocks CLI ('storage config get/list/sav

• blocks-workflow

  Design SELISE Blocks Workflows and manage them from the terminal with `blocks logic workflow list|get|save|delete|import|export|publish|unpublish`. Covers authoring a workflow graph as JSON (triggers, if/code/set-field, http/data/mail actions), importing it into a project with `logic workflow import

• blocks

  Start here for any SELISE Blocks work. Routes a plain-language request — sign-in and projects, SSO, users, roles, MFA, data schemas and records, file storage, translations, mail, notifications, workflows, functions, proxies, secrets, deployments — to the right Blocks skill, and carries the rules eve

Similar plugins