Search by

liberusoftware / notifications-filament

curtisdelicata

Notifications filament presentation adapter.

Package info

github.com/liberusoftware/module-notifications-filament

Type:liberu-module

pkg:composer/liberusoftware/notifications-filament

Statistics

Installs: 1 530

Dependents: 4

Suggesters: 0

Stars: 0

Open Issues: 0

1.1.1 2026-11-02 16:47 UTC

This package is auto-updated.

Last update: 2026-11-06 01:36:09 UTC


README

This optional package is the bounded filament adapter for liberusoftware/notifications. It presents only the matching core capability; authorization, validation, tenancy, persistence, and business rules remain in the core package.

Installation

composer require liberusoftware/notifications-filament

GitHub repository: https://github.com/liberusoftware/module-notifications-filament.

Compatibility: PHP 8.5+, Laravel 13+, Filament 5.

Presentation architecture and project hosts

The application owns panel composition, routing, session integration and deployment. This module owns its focused presentation and delegates domain behavior to reviewed public owner contracts. Keep host App aliases, duplicate records and client-only authorization outside reusable package boundaries.

Documented consumer project families:

  • Boilerplate: Shared application foundation and module composition.
  • Accounting ERP: Ledgers, tax, reporting and finance workflows.
  • Automation: AI gateways, approvals, rules and integrations.
  • Billing: Subscriptions, pricing, payments and provisioning.
  • Browser Game: Game worlds, players and community workflows.
  • Control Panel: Infrastructure and hosting operations.
  • CRM: Relationships, sales pipelines and customer service.
  • Genealogy: Family trees, research, evidence and collaboration.
  • Maintenance: Assets, work orders, schedules and field operations.
  • Real Estate: Listings, sales, lettings and agency operations.
  • Social Network: Profiles, feeds, communities and moderation.

Other web, mobile and desktop presentations are listed in the project catalog. Those skeletons provide starting structures; links do not establish feature parity, compatible releases or completed device/API integrations. Independent presentation packages keep their own Composer, npm or pub metadata.