Libraries tagged by interactive content

Generate production-style Laravel feature structure from one Artisan command: CRUD, APIs, services, repositories, tests, OpenAPI docs, modules, and AI-ready project context.

Go to Download

Interactive feedback tool for Kirby CMS websites that allows users to add contextual comments directly on page elements

Go to Download

A powerful MCP server inspector and documentation UI for Laravel — tools reference, interactive playground, scope explorer, and client connect guides.

Go to Download

yii2 interactive console with smart autocomplete and context workflow

Go to Download

Interactive terminal for running Laravel commands within tenant context

Go to Download

Interactive dictionary for Behat steps defined in multiple contexts.

Go to Download

A Laravel Nova card to display arbitrary HTML content

Go to Download

Designed for a modern health and wellness platform. Features sections for health topics, research studies, expert insights, articles, reviews, and user interaction components like FAQs, trending content, and expert consultation forms.

Go to Download

Welcome to the Svix API documentation! Useful links: [Homepage](https://www.svix.com) | [Support email](mailto:[email protected]) | [Blog](https://www.svix.com/blog/) | [Slack Community](https://www.svix.com/slack/) # Introduction This is the reference documentation and schemas for the [Svix webhook service](https://www.svix.com) API. For tutorials and other documentation please refer to [the documentation](https://docs.svix.com). ## Main concepts In Svix you have four important entities you will be interacting with: - `messages`: these are the webhooks being sent. They can have contents and a few other properties. - `application`: this is where `messages` are sent to. Usually you want to create one application for each user on your platform. - `endpoint`: endpoints are the URLs messages will be sent to. Each application can have multiple `endpoints` and each message sent to that application will be sent to all of them (unless they are not subscribed to the sent event type). - `event-type`: event types are identifiers denoting the type of the message being sent. Event types are primarily used to decide which events are sent to which endpoint. ## Authentication Get your authentication token (`AUTH_TOKEN`) from the [Svix dashboard](https://dashboard.svix.com) and use it as part of the `Authorization` header as such: `Authorization: Bearer ${AUTH_TOKEN}`. For more information on authentication, please refer to the [authentication token docs](https://docs.svix.com/api-keys). ## Code samples The code samples assume you already have the respective libraries installed and you know how to use them. For the latest information on how to do that, please refer to [the documentation](https://docs.svix.com/). ## Idempotency Svix supports [idempotency](https://en.wikipedia.org/wiki/Idempotence) for safely retrying requests without accidentally performing the same operation twice. This is useful when an API call is disrupted in transit and you do not receive a response. To perform an idempotent request, pass the idempotency key in the `Idempotency-Key` header to the request. The idempotency key should be a unique value generated by the client. You can create the key in however way you like, though we suggest using UUID v4, or any other string with enough entropy to avoid collisions. Svix's idempotency works by saving the resulting status code and body of the first request made for any given idempotency key for any successful request. Subsequent requests with the same key return the same result. Please note that idempotency is only supported for `POST` requests. ## Cross-Origin Resource Sharing This API features Cross-Origin Resource Sharing (CORS) implemented in compliance with [W3C spec](https://www.w3.org/TR/cors/). And that allows cross-domain communication from the browser. All responses have a wildcard same-origin which makes them completely public and accessible to everyone, including any code on any site.

Go to Download

Create tab-based TYPO3 content elements and page tabs with configurable interaction, animations, and autoplay.

Go to Download

This document describes the Plugin API for Lilt's Connector platform. The Plugin API is intented to be used by developers who wish to build integrations into their desired systems. The purpose of this API is to enable content transfer and status monitoring for localization projects. - Read more about the concepts and workflows in the [user guide](/docs/api/v1.0). - Test the API interactively via [Swagger UI](/api/v1.0/ui).

Go to Download

A PHP library for interacting with multiple debrid services (Real-Debrid, AllDebrid, Premiumize, TorBox, DebridLink) to download and stream torrent content with a unified API.

Go to Download

A fluent interface for interacting with web page content and urls.

Go to Download

A simple, flexible Laravel package for adding polymorphic reactions to any model. React with any text: like, love, care, or anything you want.

Go to Download

Playground: Provides an API and a Blade UI for interacting with Playground CMS, a Content Management System for Laravel applications.

Go to Download