Download the PHP package inlayphp/theme without Composer

On this page you can find all versions of the php package inlayphp/theme. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of inlayphp/theme

Informations about the package theme

Inlay Theme

Packagist PHP

Shared semantic theme contracts and presets for Inlay applications

inlayphp/theme is the PHP source of the semantic inlay.themes.v1 contract. It keeps panel and renderer customization in Laravel code while allowing every frontend package to consume a stable set of CSS-ready tokens.

For new applications, install inlayphp/design as the public design-system entry point. It reuses this serializable contract and adds CSS generation plus make:inlay-theme; this package remains the low-level compatibility builder used by existing panel integrations.

Install

For framework-neutral TypeScript helpers, use @inlayphp/theme from packages/theme/frontend.

Presets

The light presets use a soft zinc-300 control-border (#d4d4d8) for text inputs, selects, and textareas. Focus remains accent-coloured, and applications can override the token globally with control-border or locally with controlBorder.

Choose the accessibility preset directly when needed:

named() returns a copy with the same token maps and a new name. tokens() and darkTokens() merge overrides. Theme names allow letters, numbers, hyphens and underscores; token names must begin with a lowercase letter and contain lowercase letters, numbers or hyphens. Empty string token values are rejected.

Semantic tokens

The built-in base contract includes:

Applications may add semantic tokens. Keep names meaning-based rather than tied to one component so community packages can inherit the same contract. Panel forwards unknown tokens as scoped --inlay-* variables, so a token such as table-row-hover can be used by an application package without waiting for a core release.

Reading and serializing

Dark tokens are overrides, not a complete independent theme. The frontend merges them over light tokens when dark mode is active.

Renderer customization

Frontend helpers convert tokens to variables named --inlay-{token}, such as --inlay-accent and --inlay-control-height. themeToken() reads either PHP-style kebab keys or renderer-friendly camelCase aliases, which makes standalone Forms and Tables accept the same token map. Component packages may also accept local theme props and classNames; local values override inherited semantic variables.

The React and Vue Panel renderers accept either a flat token map or the serialized PHP contract directly:

For a ThemeContract, the panel uses tokens for light mode and merges darkTokens into dark mode. Standalone Forms, Tables, Infolists, Imports, Media Manager, Widgets, and Permission Manager pages accept the same ThemeSource shape, so a single application theme can be passed through an entire page without per-package adapters. Unknown semantic keys are forwarded as scoped --inlay-* variables; use them for application or community UI surfaces such as table-row-hover or billing-stage-surface.

When a PHP Theme contract is passed to a Panel, built-in light/dark tokens are bridged automatically. Unknown tokens are emitted in a scoped stylesheet under data-inlay-theme-root, avoiding global collisions between multiple panels.

Button density is intentionally semantic. Setting button-height or one of the button size tokens updates actions across panels, forms, tables, actions, permission management, media, and community components that compose the shared recipes. Use a component-level override only when a control is deliberately different, such as a compact row action.

The renderer-neutral recipe aggregate is available from @inlayphp/ui and re-exported by @inlayphp/design:

This keeps spacing, typography, focus treatment, reduced-motion behavior, and component variants in one shared vocabulary for first-party and community packages.

Testing

Related packages

All versions of theme with dependencies

PHP Build Version
Package Version
Requires php Version ^8.3
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package inlayphp/theme contains the following files

Loading the files please wait ...