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

graphcms-markdown-migrator

v0.3.2

Published

A CLI tool to automate the migration from markdown files to GraphCMS (useful for gatsby blogs for example and everything else)

Downloads

11

Readme

graphcms-markdown-migrator

This package aims to help the migration from static markdown files to GraphCMS for your blog (or whatever you've built using markdowns).

GraphCMS is a headless CMS and allows you to create entities (which are called models) and expose GraphQL mutations and queries to manage them. It also gives you an admin UI to create instances of these entities. They also have a gatsby connector, and therefore it might be just perfect for your blog, whereas you'll have a "Post" entity, and you'll manage your posts in their UI.

What does this migrator do?

You can give it a folder full of MD files, and it will try to create a "Post" entity on your GraphCMS instance, and it will create as many posts as the number of your MD files with their content in it. (it will recursively find the files between all your folders). It also uploads your media and the thumbnail of every post in the pre-configured Asset model in GraphCMS. This package will try to recreate the model from the first markdown it encounters. It means that if you have markdowns with different YAML sections, you need to create two separate folders where you'll run this migrator.

Prerequisites

  • The URL of your GraphCMS instance
  • A token with the "Management API Access" turned on. To do this, click first "edit" on the token you chose and then check the boxes like this:

Management API access graph cms token

Usage

Run:

npx md-to-graphcms --path ./your-path --url https://your-istance.com --token <token>

Options

You can provide the following optional parameters to the CLI:

Options:
  -p, --path         Path of the folder of the MD files to migrate.    [stringa]
  -u, --url          Your graphCMS URL                                 [stringa]
  -t, --token        Your graphCMS token                               [stringa]
      --thumb-field  The name of the YAML field to recognize as a post thumbnail
                     (it will upload the thumbnails automatically into the "Asset" model)
                                                                       [stringa]
      --exclude      Comma separated list of fields to exclude from your MDs
                     frontmatter: "field1, field2, field3"             [stringa]
      --model-from   The filename of the specific MD file to use to extract the
                     model (you must add the ".md" extension when specifying it)
                                                                       [stringa]
      --model-name   The name of the model to create in GraphCMS
                     (Defaults to "Post")                              [stringa]

TODO

  • Add tests
  • Implement auto-publish option