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

feltnerm-pelican-theme

v2.2.1

Published

Mark Feltner's theme for his Pelican-powered blog

Downloads

6

Vulnerabilities

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

Links

Git

Maintainers

feltnermfeltnerm

Keywords

Readme

feltnerm-pelican-theme

This the front-end module of my Pelican-powered blog.

Getting Started

To use, set your pelican theme to this theme. A few of (my current) methods for accomplishing this are:

npm

% npm install --save feltnerm-pelican-theme

Iff ./node_modules is a direct child of your Pelican working-directory, then in pelicanconf.py you add/modify the following:

THEME = 'node_modules/feltnerm-pelican-theme'

Layout

CSS

Normalize is used (as it should), Typset is used for typographic things such as post bodies, and flexboxgrid is a simple wrapper for grid-based layouts using flexbox (sorry <=IE10 users).

JavaScript

  • Sources: ./src/js
  • Bundle Destination: ./build/bundle.js
  • Dependencies:

Templates

Templates are written using Jinja and follow the pelican template conventions. They are 'compiled' with pelican. See the pelican theme documentation for more details.

Templates should follow semantic HTML5 (header, footer, nav, article, aside, section, etc.), and attempt to follow the microdata HTML5 standard as best as possible.

I am not entirely sure of the benefits of microdata in HTML documents yet, but consider this an experiment. Part of me wonders if it'd be possible to make static HTML pages into APIs if their markup was more machine readable.

Many of the templates have basic microdata elements defined, but if one is missing please submit an issue/pull-request!

Development

All sources are combined into a bundle in ./static.

Tasks

build

Runs [browserify]((http://browserify.org/) and [minifyify]((https://npmjs.com/packages/minifyify) over the sources and creates a standalone bundle with sourcemap.

This will always be the script that generates the JS bundle in origin/master and npm.