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

resonance-theme

v1.1.0

Published

scss package for all resonance projects

Downloads

5

Readme

Theme

This repository provides theme guidelines and plug-n-play style components for all Resonance properties (websites, apps and other projects).

Visit Style Documentation: https://style.resonancehealth.net

Use Node 14 LTS

Node 16 is not supported by fractal (at the time of this writing).

TODO

  • [x] Autogenate public/css/theme.css file
  • [ ] Document minimum requirements (like bootstrap5 etc)
  • [x] Abstracted use of variables and theme code separation
  • [ ] Fractal component to document these colors @Nasr
  • [x] Document an example of how to apply this project to other projects (i.e. yarn add @resonance/theme + import commands)
  • [ ] Add Patient Center components (like vertical navbar and others)

Getting Started

Import the project as a dependency. You might need a project access token. Ask an admin for this information

yarn add "https://anonymous:[email protected]/resonance/theme.git#master",

NOTE: The #master at the end will peg the project to whatever is the currently release theme.

If you don't wish to customize anything, simply add this to your SCSS loader:

@import 'resonance-theme/src/app.scss';

If you wish to customize colors for the bootstrap (other than what resonance theme recommends), use the following snippet

// CUSTOMIZE YOUR VARIABLES HERE (follow whats in resonance-theme/src/variables.scss)

// User variables
@import 'resonance-theme/src/variables';

// Configuration & utilities
@import 'resonance-theme/src/theme/variables';
@import 'resonance-theme/src/theme/mixins';
@import 'resonance-theme/src/theme/utilities';

// Bootstrap
@import 'bootstrap/scss/bootstrap';

// Layout & components
@import 'resonance-theme/src/theme/reboot';
@import 'resonance-theme/src/theme/components';

// User custom styles
// Good place to @import your own styles

Fonts and Images

To correctly include font families for a project as well as images, override the default $resonance-sans-font-path and $resonance-images-path variable.

Development

Install dependencies, and start watcher:

yarn
yarn serve

Remember the yarn serve command will start two processes: gulp watch, which is responsible for compiling the sass code in to css files. And it starts the fractal dev server. The gulp watch command is backgrounded so you might have to kill that at end of development. If you don't like this behavior simply start the two processes separately:

./node_modules/.bin/gulp watch
yarn fractal:start