Download the PHP package waynestate/wayne-ui without Composer

On this page you can find all versions of the php package waynestate/wayne-ui. 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?

Informations about the package wayne-ui

WayneUI

The Wayne State University design system. One set of brand tokens, one set of components, four ways to use them, and an accessibility bar that is a command anyone can run rather than a claim a README makes.

2.0 is a hard break from cit-web-infra/wayne-ui (1.x). 1.x was Bootstrap 3 and jQuery. It is archived and there is no compatibility shim. See MIGRATING.md for the 1.x to 2.0 mapping.

Pick your path

WayneUI meets you where you already are. All four paths render the same markup and carry the same accessibility guarantees. Vue is one of the four either way; which guide you want depends on whether Laravel is already wiring the chrome's data for you.

You are building Start here
A static site, no build step docs/static-html
Raw PHP, no framework docs/raw-php
Laravel with Blade docs/laravel-blade
Laravel with Inertia and Vue docs/laravel-inertia
Vue with no Laravel docs/vue

Static site, with no build step

Two tags, and write HTML:

The fonts, the marks and the icon sprite follow from those two, so there is no folder to copy unless the machine has no network at all.

Laravel

Vue

daisyUI or shadcn-vue, your choice

WayneUI does not fork its components per framework. WSU components are built on one layer of semantic --wsu-* tokens, and daisyUI and shadcn-vue are thin adapters over that layer:

So <button class="btn btn-primary"> and <Button> come out in the same WSU green, from the same source of truth. Use daisyUI if you want Tailwind without a JavaScript pipeline. Use shadcn-vue if you have Vite. Neither is required. The WSU chrome works with wayne-ui.css alone.

Two templates

Both are application templates. The only difference is who can reach them, and therefore how much university identity they carry.

Accessibility

WayneUI targets WCAG 2.2 Level AA as a floor, and AAA wherever the brand palette allows. Each of these is a command that fails on a violation, and pnpm verify runs all of them:

.gitlab-ci.yml runs the same commands with nothing marked allow_failure, but this GitLab instance has no runners and no pipeline here has ever executed. The checks are real; running them is still something a person does.

See Accessibility and the shipped VPAT.

The theme follows the operating system. An explicit choice, stored under wsu-theme, wins over it; light is the fallback when there is neither. Someone who has set their machine to dark has already said what they want, and should not have to say it again in every application. Dark is a first-class theme, not a courtesy: every color pairing is contrast tested in both.

Repository layout

Development

Brand

Colors and type come from the WSU Identity Style Guide, and the ramps match waynestate/base-site stop for stop, so green-400 means the same thing in both. Primary green is PMS 561c #0C5449 and primary gold is PMS 1225c #FFCC33. If the guide changes, change the tokens rather than a component.

Questions

Open an issue for anything reproducible, so the next person to hit it finds the answer already there. For adopting WayneUI in an application, a component that does not exist yet, or an accessibility finding you would rather not file in public, write to [email protected].

License

MIT for the code. Wayne State trademarks are not covered by it. See LICENSE.md.

All versions of wayne-ui with dependencies

PHP Build Version
Package Version
Requires php Version ^8.2
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 waynestate/wayne-ui contains the following files

Loading the files please wait ...