npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

aliro-orchestrator-branding

v1.4.0

Published

Client logos, styling and copy to apply to Aliro Orchestrator frontend builds.

Downloads

71

Readme

Aliro Orchestrator Branding

This repository contains branding assets and packages for use in white-label aliro-orchestrator-frontend compilation for creating a client-specific frontend build.

This repository also contains style assets for the QNO Orchestrator (qno-frontend).

Required client branding assets directory structure

  • src/<client-name>/copy/brand-copy.json
  • src/<client-name>/images/logo-header-left.png
  • src/<client-name>/images/logo-header-right.png
  • src/<client-name>/styles/brand-style.scss
  • src/<client-name>/styles/css-vars.scss
  • packages/<client-name>-branding/package.json

To publish a branding package

  • Change directory to ./packages/<desired package>
  • If update to package is a bugfix, do npm version patch. Otherwise, run npm version minor.
  • Publish contents via npm publish (pass --dry-run to perform a test run, if desired).
  • Open PR to merge updated branding package package.json files.

Color format

Because CSS color variables from this package may have alpha channels applied or otherwise be passed to CSS color functions, all colors must be in raw RGB format.

Example:

  // correct
  --branding-primary-color: 255 0 0;

  // incorrect
  --branding-primary-color: rgb(255, 0, 0);
  --branding-primary-color: #FF0000;