A page of a site as a React component and its props, the same from any framework: the first visit an HTML shell holding the page, a visit within the site the page in JSON (header X-Omnibridge), the JavaScript side rendering it and following the site's links without reloading.
A Composer plugin that knows no package: patches and stub providers declared by packages in extra.omnibridge
The small contract a page rendered with Twig asks of any framework (path, asset, trans), and the Twig extension that provides it where the framework does not.
The storage glue of omnibase sites, framework-free: the naming strategy that turns their entities into their tables, the UTC date types, and an entity manager built with them, for any framework reading the same database.
omnibridge/symfony: the Symfony side of omnibase - the framework packages the core no longer requires
omniscient/omnibridge: the host contracts (urls, translations, locales, access, sessions, tokens, files, routes, environment) and their registry, the core of the omnibridge family
The Laravel host of omniscient/omnibase: its Fondation contracts answered by Laravel's services, Doctrine and Twig through omnibridge.
To associate your repository with the omnibridge topic, visit your repo's landing page and select "manage topics."