Skill UI

This skill guides developers on integrating Okta as an external Identity Provider (IDP) for Webiny. It replaces default authentication methods (like Cognito) by utilizing the OpenID Connect (OIDC) standard. The process involves setting up an API configuration class to map Okta's JWT claims to Webiny identities, and creating a React extension component to wire the issuer URL, client ID, and configuration path, enabling seamless Single Sign-On (SSO) using Okta.

This pattern provides a robust method for extending and customizing existing GraphQL APIs. Developers can implement `GraphQLSchemaFactory` to add custom root queries and mutations, injecting complex business logic and use cases directly into the API layer. It fully supports per-resolver dependency injection (DI), ensuring that every resolver has access to critical request-scoped context, such as identity and tenancy, making it ideal for building modular, enterprise-grade backend services.

This guide explains the universal Dependency Injection (DI) pattern used across all Webiny extensions (API, Admin, CLI, Infrastructure). It details how to correctly implement constructor injection using the `dependencies` array to access core services like Logger, BuildParams, CMS use-cases, and IdentityContext. Mastering this pattern is crucial for building maintainable, type-safe, and cohesive Webiny extensions.

This pattern provides a comprehensive guide to implementing domain event handlers (before/after hooks) within the Webiny framework. It emphasizes the 'thin orchestrator' principle, requiring handlers to delegate all business logic to reusable service abstractions or UseCases for maximum reusability. Furthermore, it details the process of defining, publishing, and reacting to custom domain events, ensuring a clean, decoupled architecture.

This module provides essential architectural abstractions for structuring complex applications using the Webiny framework. It defines core types for various system components, including Admin panels, APIs, Command Line Interfaces (CLI), Infrastructure management, and Project logic. Developers must utilize these imported abstractions to ensure strict type safety and clear separation of concerns in their code.

Provides a standardized and robust skeleton for developing full-stack extensions that integrate both a backend API service and a frontend Admin UI. This pattern enforces clear separation of concerns, utilizing shared domain layers for data consistency while ensuring that API and Admin code are correctly registered using specific entry points. Ideal for complex applications requiring unified management interfaces and robust backend logic.

This skill provides a robust mechanism for extending an existing API gateway by adding custom, non-GraphQL HTTP endpoints (GET, POST, PUT, etc.). Developers can implement the Route.Interface and register it using the <Api.Route> component. It supports full Dependency Injection (DI), providing framework-agnostic Request and Reply objects, making it ideal for integrating complex business logic directly into the API structure.

This skill provides a powerful mechanism for modifying and extending AWS infrastructure using Pulumi handlers and dedicated declarative components. It allows developers to manage complex cloud setups, including configuring OpenSearch, VPC networking, resource tagging, custom domains, blue-green deployment strategies, and implementing environment-conditional configurations (e.g., production vs. development).

This guide details the complete architecture and organizational principles of a Webiny project. It covers the core concepts of the flat folder structure, the role of the central `webiny.config.tsx` file, and how to register various types of extensions (API, Admin UI, Infrastructure, and CLI Commands) using declarative JSX components. Use this when developers need to understand where custom code belongs and how to integrate different functional components into the platform.

The official SDK for integrating Webiny's Headless CMS and File Manager into external applications (e.g., Next.js, Vue, Node.js). It provides a robust TypeScript interface for reading, writing, updating, and managing content entries. Features include listing, filtering, sorting, handling content revisions (read vs. preview mode), and ensures type safety using generics, making complex data operations reliable and scalable.

This guide provides comprehensive migration patterns for upgrading existing Webiny v5 code to the v6 architecture. It details key architectural shifts, such as replacing ContextPlugins with Dependency Injection (DI) services, converting event subscriptions to EventHandler features, and restructuring plugin arrays into feature registrations. It is an essential resource for developers and AI agents performing major framework upgrades.

This skill guides developers on creating custom, configurable, and data-driven editor components for the Webiny Website Builder. It details the use of `@webiny/website-builder-nextjs` to register components, define various input types (text, number, color, select), manage themes using CSS variables, and integrating Server Components to fetch CMS data. Ideal for building robust, genuine WYSIWYG editing experiences within a Next.js environment.