netlify-cms | A Git-based CMS for Static Site Generators | Content Management System library

After having access to the repo (which runs on Gatsby) I found that /styles/ folder when searched was inside the /public/ folder which is generated by gatsby, this pointed me to the same error that referenced the chunk error "componentChunkName": "component---src-pages-styles-js", I then searched for this file which existed in the .cache, this file showed me the error was coming from @emotion trying to compile the src/pages/styles.js file that is used by index-old.js.

It seemed that Gatsby was interpreting /src/pages/styles.js as a normal static page to build, but because it is returning a function that returned emotion JSX it couldn't build properly as Gatsby expects all .js files to return React JSX code.

It turned out in this project, these files wasn't actually used anymore so simply deleting them fixed the issue. If it was used though, simply having styles.js somewhere other than the /src/pages folder would fix this. I'd recommend having a views folder where you store all pages and styling relative to it to avoid Gatsby trying to compile pages from styling.

I could "gatsby develop" but I think when I'm adjusting photo data in "page-data.json" which stored public\page-data\index I "gatsby develop" won't start

You should never edit manually the content or the code inside the /public folder directly. Keep in mind how Gatsby works: when you run gatsby develop or gatsby build, webpack compiles and bundles everything under /src folder to create the /public one: this is autogenerated and it is rebuilt when you change anything on your /src folder. If you change anything inside the public folder manually without changing the source, it will be lost in the next compilation because the source doesn't includes the changes. So, all changes must be done in the /src folder.

In this case, the error is rising because you changed the public folder directly so the references of the assets page-data.json have changed.

To change the coffee.png image, you need to change the static folder. The static folder is a "special" folder that is cloned inside the public folder keeping the exact internal structure. As the name suggests, is very useful to use for static assets (the ones that rarely change).

Once you change the coffe.png image for your desired one, you just need to change the references of coffee.png to the new one (unless they are called the same).

That said, this kind of static change may force you to reload the gatsby develop (stop and rerun) process to see the changes. If the image still without changing, clean the cache by running gatsby clean before rerunning the gatsby develop command.

By using 'nonce-value' you can get rid of 'unsafe-inline' only, but not of 'unsafe-eval'.

'unsafe-eval' in Netlify is required to compile JSON to JS code, but you can get rid of 'unsafe-eval' too. Just update ajv-json-loader to use AJV 7 and Standalone mode and configure webpack config to use the updated loader. See nitty-gritty here.

This issue can have multiple solutions depending on what's causing it. Normally, what usually happens is that Gatsby can't create the thumbnail node because has an unrelated type (String) where it should be an image node because the relativity between parent-children nodes is lost somehow.

Potential solutions:

• Run gatsby clean: cleans the cache. Then, gatsby develop the project again.

• Check the media_folder and public_folder in your config.yml: in your case, to me, they both looks good.

• Use gatsby-remark-relative-images-v2 plugin: Netlify CMS doesn't fully support relative paths (yet) so in the meantime, you may need the help of that plugin. This is because the image is outside the node folder.

  After installing it. Just add it as an option of the

You could use a so-called "gaps-and-islands" approach

I'm not sure how to tell Gatsby to create a single page with possibility to inject a filter value in order to pass it to the page query.

You can't. The only way to filter data in a page query is by passing data using the context. Like you are doing in with the tags page:

Gatsby's team is actually working on reducing the build time by adding some "cache" features. You can follow the stack trace in their releases notes, they are still in beta testing (some of them are focused mainly on gatsby develop.

If you want to try it them to check if it improves the build-develop time, you just need to upgrade Gatsby to the latest version (^2.28) and:

there a similar way to use "custom" data collections with Gatsby?

Sure there is. Create a /static folder at the root of your project (if you don't haven't it created yet). There create another /admin folder and place a config.yml there. The final structure is: /static/admin/config.yml.

Basically, the config.yml file is where your collections and the CMS will be configured based on the broad documentation from Netlify. It also exposes a localhost:8000/admin (or yourDomain.com/admin on production) URL to log into your private CMS and perform the CRUD actions to your collections.

The case you are describing may look something like:

According to some threads about that starter, there's a bug about the Sass loaders that causes this issue. You have many solutions provided in this GitHub thread:

• Add options to the gatsby-plugin-sass: