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

drasil

v0.0.1

Published

A structured content management system (w/ HTTP API). (Currently in Progress)

Downloads

4

Readme

Drasil

A JavaScript/Node based CMS, built around structured data. (e.g. RDF)

  • A main goal is to design a content management system, thats it, the system should not care how the content is consumed.
  • The content should be exposed through web services, and can be consumed by javascript, ios, etc
  • The backend must be flexible, we need to be able to swap out data storage modules
  • there should be an optional data caching module. again, it should be able to be swapped out.
  • The UI should be based on bootstrap, or something similar, we can also use ASP.NET MVC for the quick Admin UI

Why?

  • Most Content Management systems out there provide some crazy way to get the content from the system, to the site, this is a waste when you want full control over how content is rendered, so why not just have an admin export the content as web services?