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

@planningcenter/tapestry-design-tokens

v5.0.1

Published

Tokenized values from the Tapestry Design System

Downloads

14,684

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

kylemellanderkylemellanderjonsuhjonsuhkeolakeolatimmorgantimmorgandanottdanott

Keywords

Readme

Immutable, tokenized values defined in Figma by the Design Division, built with Style Dictionary.

  • Primitives and alias tokens are managed by the UX team.
  • Component-specific tokens are managed by the Design Engineering team.

Using Tokens

CSS Custom Properties:

Include this stylesheet in your CSS/SCSS manifest:

  • @planningcenter/tapestry-design-tokens/dist/tokens.css

Adding New Tokens

  1. Navigate to the appropriate Figma file for the tokens you need. UX is responsible for primitive and alias tokens while Design Engineering is responsible for component-specific tokens.

  1. Export a JSON of Figma variables using the Planning Center Design Tokens plugin. Design Tokens Figma plugin

  2. Download and save the file to the src/json directory of this Design Tokens repo.

  3. Create a branch off main, commit the files, and open a PR.

Publishing

  1. Open a PR with the JSON changes
  2. Once merged, the PR tagged pco-release-pending will rebase/update to include the new changes
  • Adjust the Github tags on that PR to reflect which version type (major, minor, patch) reflect the changes introduced
  1. After that PR is merged, the automated workflow will handle building + publishing the package contents to NPM ✨

Documentation

  • Documentation is available here and will be updated through the Github action when a new package version is released/deployed.
  • The documentation site is available locally using yarn start