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

uoydesignpatterns

v1.7.1

Published

This repository holds the design patterns used on the University of York's website (http://www.york.ac.uk).

Downloads

4

Readme

UNIVERSITY OF YORK DESIGN PATTERNS

Codacy Badge Build Status

This repository holds the design patterns used on the University of York's website.

Setting up your development environment

You will need to have NodeJS (including NPM), Git, Ruby (including RubyGems) and Compass installed on your machine. On Windows, the easiest way to do this is with Chocolatey and on Mac you can use Homebrew.

You'll also need a global install of Grunt (a task runner), Yarn (a package manager) and BackstopJS (a visual regression tester), which you can do by typing:

npm install -g grunt-cli
npm install -g yarn
npm install -g backstopjs

Getting ready

After cloning this repository, you will need to run:

yarn install

This will load all the necessary modules for you to continue development.

You're now ready to start making stuff!

Active development

To work on the front-end designs, run yarn build in the terminal. This will create the active templates and start a local server, which will live reload as you code.

Building the documentation

Running a yarn build task will create a build directory, which will contain the minified CSS, the uglified JS, the optimised images and the HTML pages ready to deploy to a server.

Building for release

To build a release version, you need to follow the instructions in our development docs.

Essentially, we employ a continuous build and deployment system that takes commits to the code base, builds them and automatically deploys successfully built files to a preview or live server, depending on the commit.

Custom styles

Minified stylesheets for TinyMCE and Formstack are created as part of the build process.

A note about development

The dev branch of this repository is the one we use to build our CSS and JS for front-end deployment. Most new work should be started in a new branch in Git.

To set up a new branch, type:

git checkout -b "new-branch-name"

This will create, and switch to, a new branch in Git. Make your changes as usual, then run git add and git commit -m "Your concise and descriptive commit message". When you come to push your changes you'll need to do a slightly different command in order to create the new branch on the remote:

git push -u origin new-branch-name

You can find more about our recommended branching, versioning and naming conventions in our development docs

We will merge any signed-off branches into dev and they will be deployed in the next release.

Testing with Browserstack

We are continually improving our testing and QA processes. Part of this means using some great tools to make sure we catch and squash as many bugs as possible. One of those tools is Browserstack. We use their screenshots tool to check our work in as many browsers, platforms and front-end scenarios as we can.