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

@openagenda/bs-templates

v2.5.0

Published

openagenda bootstrap templates

Downloads

96

Readme

Overview

Project for sassing openagenda styles.

To get started, run server.js, a tiny express server to serve rendered styles.

So:

npm install ln -s node_modules/font-awesome/fonts fonts cd templates/event-form ln -s ../tinymce/skins/lightgray/fonts fonts

and then:

npm start

Final css usage

  • Ensure all wanted style is added in the proper compiled/ scss file and npm run build to get the final css file. Require that where you please.

Rules

  • Avoid loosely identified general styling rules. If you think a style may be useful for other pages in the future, put it in a separate scss file, but keep it in the folder of the project you are working on. When the day comes that the file is effectively used elsewhere, it can be moved at that point

  • the ejs templating engine is used to build template pages for its partial feature. No other feature is used. So .ejs files are basically html files with occasional 'include' statements

  • scss files of each template import all the styles they need.

  • partial scss files start with an underscore

  • partials start with an underscore they often match a corresponding scss file.