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

@pernod-ricard-global-cms/cblcolourpalettes

v0.4.1

Published

Colour themes

Downloads

928

Readme

Colour Palettes

Import colour palettes js into the preview as well as the main js file for the frontend with:

import colourPalettes from '<path to js file>';

The data for the colour palette js should be an object containing all the names of the colour palettes you wish to use. The value of each palette name in the object should be an array of hex strings. There also needs to be a property in the object called pickerNames the value of which is an array of strings that are the names of the acf select fields you want to listen to changes on. If the data file is json or js you can import it like this:

import colourData from 'Assets/js/modules/colour-palettes/colour-data';

then pass the imported data to the colour palettes js like this:

colourPalettes(colourData);

For the code to know what palette to apply on the front end it looks for a data attribute on the html tag called data-currentcolourpalette. The value of this needs to passed in to the template. Something like this:

{% set currentPalette = "default" %}
{% if post.product_palette_picker is defined and post.product_palette_picker is not empty %}
{% set currentPalette = post.product_palette_picker %}
{% endif %}
<html prefix="og: http://ogp.me/ns#" lang="{{ gtp_language_code() }}" data-currentcolourpalette="{{currentPalette}}">

Finally in the admin you will need a custom field to set up the select field for switching palettes. The name product_palette_picker in the above example is the name of the custom field. The names in the choices input section should correspond to the names of the palettes in the data file that you wish to select. eg:

default : No palette (defaults)
mizunara : Mizunara
chivas12 : Chivas 12