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

pallote-css

v0.2.37

Published

CSS component library

Downloads

36

Readme

Pallote CSS

Welcome to Pallote CSS! Pallote CSS is an open-source CSS library aimed at providing developers with a collection of reusable and customisable components and styles streamline the development of web projects.

Usage

Installation

NPM

To install Pallote CSS via npm use:

npm install pallote-css

Then import the global style file in your SASS file, like this if you are using SASS:

@import '../node_modules/pallote-css/dist/pallote.scss';

Or if you are using regular CSS, locate the file, copy/paste them into your project and import them into you <head>.

<link rel="stylesheet" href="link/to/file/pallote.css">

CDN

Alternatively, you can link via a CDN. Simply copy/paste this code in between the head tag of your website. Make sure to add the version number, as next version could introduce breaking changes.

<link rel="stylesheet" href="https://cdn.jsdeliver.net/npm/[email protected]/dist/pallote.min.css">

Using Components

Once the library is imported, start using the components by adding appropriate class names to your HTML elements. Refer to the documentation for each component to understand its usage and available customisation options.

<button class="button button--primary">Primary Button</button>

Customisation

Pallote CSS allows for easy customisation of components to match your project's design.

Custom variables

The framework has a set of built-in variables that create the design look and feel. To override them, add a variable with the same name in your Sass style file. To see the full list of variables, see documentation.

$primary: #007A1E;

@import '../node_modules/pallote-css/dist/pallote.scss';

Custom components styles

To change a component style, see the documentation for each component and add create an instance of the class with new properties in your style file.

@import '../node_modules/pallote-css/dist/pallote.scss';

.button {
  text-decoration: underline;
}

You can also override default styles by defining custom CSS rules in your project's stylesheet.

.custom-button {
  text-decoration: underline;
}

Documentation

For detailed documentation on each component and customisation options, please refer to the documentation website: pallote.com.

The documentation is built with Jekyll. For more information on how to run the repo and contribute, see section below.

Contributing

Contributions are welcome! If you find any bugs or have suggestions for new features, feel free to open an issue or submit a pull request. This documentation serves as a guide for contributors on how to effectively contribute to the project.

Run the project locally

  • Fork the repository and clone it
  • Install Jekyll; Jekyll is a Ruby Gem that can be installed on most systems (installation manual).
  • Install dependencies
npm install
  • Start a localhost server
npm run dev

Make changes

  • Checkout to develop branch
  • Create a new branch on which to write your code
git checkout -b feature-name-of-branch

Make sure to add the prefix feature- to the name of your branch

  • Write your code. There are two locations for the style files:
    • dist/styles folder, which are the core styles of the library
    • assets/styles folder, which are the documentation specific styles

You don't need to run any additional command to compile sass files, it does it automatically with npm run dev Remember to add any new class or property to the doc

Submit your code

  • Before submitting a pull request, make sure to test your changes thoroughly. Ensure that your changes do not break any existing functionality and that they are compatible with different browsers.
  • Once the changes are made and tested, submit a pull request to the main repository. Be sure to include a clear description of all the changes you've made.
  • When changes are approved, they will be merged into the develop branch for testing, and will be published to the master branch on the next release.

Reporting Issues

If you encounter any issues while using Pallote CSS, please report them by opening an issue on the GitHub repository. Be sure to include a detailed description of the problem and steps to reproduce it.

Methodology

Pallote CSS is based on an adapted version of BEM terminology (for Block Element Modifier). More information on naming conventions and methodology is in progress.

License

This project is licensed under the MIT License - see the LICENSE file for details.