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

gatsby-theme-developer

v1.5.1

Published

## Demo

Downloads

7

Readme

Gatsby Minimal Theme for Developers

Demo

You can find here a demo website: https://www.miguelangelmartin.me

Quick Start

mkdir my-site
cd my-site
yarn init

# install gatsby-developer-theme and it's dependencies
yarn add gatsby react react-dom gatsby-theme-developer

You can add now the yarn scripts to your package.json file

{
  "scripts": {
    "build": "gatsby build", 
    "clean": "gatsby clean",
    "develop": "gatsby develop"
  }
}

Then create the gatsby-config.js file:

touch gatsby-config.js

And add the theme configuration to it:

module.exports = {
    plugins: [
        {
            resolve: "gatsby-theme-developer",
            options: {
                title: "Title of your site",
                subtitle: "a short subtitle for the meta title on the home page",
                description: "A minimal theme for your personal blog or webpage",
                siteUrl: "https://...com",
                defaultPreviewImage: "/og-default.png",
                author: {
                    name: "Your Name",
                    bio: "Software Engineer",
                    avatar: "https://mywebsite.com",
                    links: {
                        twitter: "https://twitter.com/username",
                        linkedin: "https://linkedin.com/in/username",
                        github: "https://github.com/username",
                        instagram: "https://instagram.com/username",
                        mail: "mailto:[email protected]"
                    }
                },
                links: [
                    {
                        title: "Home",
                        href: "/"
                    },
                    {
                        title: "About me",
                        href: "/about-me"
                    },
                    {
                    title: "Blog",
                    href: "/blog"
                    }
                ],
                articlesPerPage: 4,
                language: "en"
            },
        },
    ],
}

That's it, you can now run your gatsby site using

yarn gatsby develop

This will run a local web server and create the content and static folders with all the required files to run your website.

Adding content

The content need to be stored in the content directory as markdown files.

Every markdown file need to have a frontmatter section in it. Here is an example:

---
date: 2020-11-20 00:30:03+00:00 slug: /2020/hello-world/ title: Hello World template: post coverImage: /the-image.jpg tags:

- Writing draft: false description: "This is your first article, you can find it in the /content directory"

---

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Fusce eu lorem eget metus venenatis dignissim.

As you see the frontmatter section has some variables, some are required but others not

| variable | required | description | |--------------------|------------|-------------------------------------------------------------------------------| | date | true | the ISO 8601 date of the article or page YYYY-MM-DD HH:mm:ss±hh:mm | | slug | true | the path for the article or page, for example /2020/hello-world | | title | true | the title of the article or page | | description | false | the description for the article or page | | draft | true | is the article is published or not | | template | true | the template: the possible values are: post or page | | coverImage | false | the cover image for the article | | tags | false | an array of YAML tags |