Netlify CMS config.yml sample

[vasfvitor]

I'm very new to gatsby, JS and dev in general, with that in mind:

I'm working on a config.yml file for Netlify CMS to create blog posts based on what this starter needs to create the post, so far this model is working in localhost, I tried to deploy to Netlify but the build failed (non related to this file).

All this was made possible by the docs in netlifycms.org

config.yml

backend:
  name: github # Refer to https://www.netlifycms.org/docs/authentication-backends/ for auth backend list and instructions
  branch: master # Branch to update
  repo: your-user/gatsby-advanced-starter # Repo for pushing new commits. Make sure to replace with your repo!

commit_messages:        #I copied this section from a Netlify CMS demo
    create: 'Create {{collection}} “{{slug}}”'
    update: 'Update {{collection}} “{{slug}}”'
    delete: 'Delete {{collection}} “{{slug}}”'
    uploadMedia: '[skip ci] Upload “{{path}}”'
    deleteMedia: '[skip ci] Delete “{{path}}”'

media_folder: "content/images"     #absolute project path. Probably ContentDir/images
public_folder: "images"     #path that will be parsed to .md file (following the .mdx default post structure)
# publish_mode: editorial_workflow   #enable the flow: draft -> in review -> ready (published) You can remove this line if you think it slowdown your work

collections: #option in the CMS panel
  - name: "post"
    label: "Blog Post"
    folder: "content" # posts output folder (.md filetype)
    create: true
    slug: "{{year}}-{{month}}-{{day}}-{{slug}}" # filename format
    fields:
      - {label: "Title", name: "title", widget: "string"}               
      - {label: "Cover", name: "cover", widget: image}
      - {label: "coverAlt", name: coverAlt, widget: "string"} 
      - {label: "Description", name: "description", widget: "string"}
      - {label: "Body", name: "body", widget: "markdown"}
      - {label: 'Category', name: 'category' ,widget: 'string'}
      - {label: 'tags', name: 'tags', widget: 'list' }
      - {label: "Publish Date", name: "datePublished", widget: "datetime" }
      - {label: "Date Modified", name: "dateModified", widget: "datetime"}

The folders needs to be adjusted per project. The Gatsby Advanced Starter uses the path images to build the posts, so public_folder path must remain unchanged.

[vasfvitor]

Oh, just found out that the theme 'amaranth' already have a config.yml .
facepalm

[Vagr9K]

To be honest the theme folder is the last place somebody would expect to find a NetlifyCMS config.

The main reason why it isn't in the root of the starter, is that the static template content between the themes is shared, so this prevents duplication.

That being said after this discussion I'm rethinking that approach and wondering if staticDir and assetDir should be set separately for the starter root.

[vasfvitor]

What is this staticDir? I didn't find any references. Did you mean contentDir?.
Also I didn't understand at all what is it you're rethinking, I mean, in the starter gatsby-config.js I added a path for contentDir but assetDir I left undefined. And there's any duplication, and I think nothing is wrong.

[Vagr9K]

What is this staticDir? I didn't find any references. Did you mean contentDir?.

Yes. That's the one.

Also I didn't understand at all what is it you're rethinking, I mean, in the starter gatsby-config.js I added a path for contentDir but assetDir I left undefined. And there's any duplication, and I think nothing is wrong.

Some people might end up missing the configurations needed to get the content and asset directories up. Or end up missing the fact that the config.yml already exists. It's not user friendly basically.