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

metalsmith-get-contentful

v1.0.7

Published

A metalsmith plugin to grab contentful files

Downloads

9

Readme

Build Status License NPM Downloads Known Vulnerabilities Coverage Status

metalsmith-get-contentful

A Metalsmith plugin to read content from the Contentful API.

Lightweight wrapper around the Contentful API to query content, get the content's fields, and place the fields into metalsmith "files" for later processing. Typically done before the markdown stage.

This plugin works best if your Contentful Content has fields that match up to the YAML data needed for your metalsmith template engine. For example, they should probably have a "title", "template", and, most importantly, "contents".

If your content has a mismatch, see options.msFiles.addYAML and options.msFiles.postProcess().

Usage

To grab all "projects", use their field "slug" as a filename, and put them under the path "/projects/{slug}.md"

var getContentful = require('../getContentful.js');
...
.use(getContentful({
      client: {
         space: '<space_id>',
         accessToken: '<access_token>'
      },
      query : {
         content_type: 'project'
      },
      msFiles : {
         idField: 'slug',
         filename: "projects/${id}.md"
      }
   }) )

Options

client: required arg for Contentful.createClient(client)

You must provide:

  • accessToken:
  • space:

query: arg for client.getEntries(query)

Default is {}.

msFiles: how to manipulate and place the content into metalsmith

  • idField: field to use for id. default is 'slug'. falsy means use sys.id
  • filename: pattern to create the metalsmith "filename" based on id. default is "posts/${id}.md"
  • postProcess(): Default is null. If present, the content will be replaced by postProcess(content). For example, if you need to rename fields.
  • addYAML: default is {}. Gets added to each result. Useful if you want to add fields such as a template
  • metadata: default is null. If present, also place all the data into metalsmith.metadata() here.

Notes, Todos, and Caveats

If the "file" is already present, getContentful calls done() with an Error.

After writing this, discovered a very similar approach and code in Bitbucket contentful-data

A different approach is in contentful-metalsmith

leviwheatcroft/metalsmith-contentful also gave me a few ideas.