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

emails-templates

v1.0.2

Published

Basic template for a Foundation for Emails project.

Downloads

1

Readme

Email templates

Usage

Each email template is grouped by projects, and they are located under src/pages folder.

Each project is deployed separately and has their own SendGrid accounts.

Please follow Foundation email template best practises. Read about Foundation email template here.

Template variables

When target environment is staging or production, Handlebars variables are not replaced.

If you want a variable to be always replaced, variable should have $ prefix.

<!-- `title` is not replaced for staging and production -->
<h1>{{title}}</h1>

<!-- `$title` is always replaced -->
<h1>{{$title}}</h1>

Create new template

In order to create a new template for staging and production use this command

yarn create-template

Build

Specify the target environment in command with --env argument. Default is local.

When environment is not local, templates are minified and CSS styles are inlined.

# Build for staging
yarn build --env staging

# Send email with production build
yarn email --env production