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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@jsonblog/schema

v3.1.0

Published

A community-driven schema for blog content that emphasizes portability and content ownership

Readme

JsonBlog Schema

npm version CI License: MIT TypeScript

A community-driven schema for blog content that emphasizes portability, extensibility, and content ownership. JsonBlog lets you define your blog's content in a structured way while maintaining complete freedom over how it's presented.

Note: JsonBlog is in early development. The current schema focuses on core functionality, and we expect to add more blog-specific fields based on community feedback and real-world use cases. If you need fields that aren't yet supported, please open an issue to discuss them!

Why JsonBlog?

  • Content Ownership: Your blog content in a portable, standardized format
  • Platform Independence: Switch between any static site generator that supports the schema
  • Flexible Content Sources: Mix local, remote, and decentralized content seamlessly
  • Future-Proof: Your content remains accessible even as platforms come and go
  • Community-Driven: Schema evolves based on real-world needs and use cases

Schema (v1.0.0)

interface Blog {
  // Core blog information
  site: {
    title: string;
    description?: string;
    image?: string;
    email?: string;
    phone?: string;
    url?: string;
    summary?: string;
    profiles?: {
      network: string;
      username?: string;
      url?: string;
    }[];
  };

  // Author information
  basics: {
    name: string;
    label?: string;
    image?: string;
    email?: string;
    phone?: string;
    url?: string;
    summary?: string;
    location?: {
      address?: string;
      postalCode?: string;
      city?: string;
      countryCode?: string;
      region?: string;
    };
    profiles?: {
      network: string;
      username?: string;
      url?: string;
    }[];
  };

  // Blog posts
  posts: {
    title: string;
    source?: string;
    description?: string;
    position?: string;
    url?: string;
    startDate?: string; // YYYY-MM-DD
    endDate?: string; // YYYY-MM-DD
    summary?: string;
    highlights?: string[];
  }[];
}

Versioning

The schema follows semantic versioning:

  • MAJOR: Breaking changes to required fields
  • MINOR: New optional fields or features
  • PATCH: Documentation updates or bug fixes

Current stable version: 1.0.0 (backwards compatible with v0.x)

Tools and Ecosystem

Contributing

JsonBlog is a community project and we welcome contributions of all kinds! Here's how you can help:

1. Propose Schema Improvements

Have ideas for new fields or improvements? Open an issue with:

  • Your use case description
  • Example JSON showing how you'd use it
  • Benefits of adding these fields
  • Any backward compatibility considerations

Common areas for expansion include:

  • Blog-specific metadata (tags, categories, series)
  • Content management fields (draft status, publish dates)
  • SEO-related fields
  • Analytics integration
  • Comments and interactions

2. Share Your Experience

  • Create and share blog generators using the schema
  • Build tools around the ecosystem
  • Write tutorials or blog posts about your JsonBlog setup
  • Share example blog configurations

3. Development

# Clone the repository
git clone https://github.com/jsonblog/jsonblog-schema.git
cd jsonblog-schema

# Install dependencies
npm install

# Run tests
npm test

# Build TypeScript types
npm run build

4. Review and Discuss

  • Join schema discussions in GitHub Issues
  • Help review pull requests
  • Test proposed changes in your projects
  • Share feedback on schema evolution
  • Help maintain backward compatibility

5. Documentation

  • Improve the README
  • Add examples and tutorials
  • Translate documentation
  • Document best practices and patterns

Community

License

MIT