After switching from Jekyll to Gatsby, there have been some tips I wish I would have had getting setup.
Having problems building?
Build problems usually reveal issues with developer code. Sometimes its an issue with Gatsby caching. You can try:
nvm install rm -rf .cache node_modules public npm i gatsby build
nvm install rm -rf .cache node_modules public # sometimes it IS `npm i` vs. `yarn` yarn gatsby build
HTML is not rendering within Markdown files?
html within markdown is a plus and these changes can look fine in development.
One potential reason for issues is Gatsby Remark Plugins, like Gatsby-Remark-Images.
My initial somewhat hacky fix is removing some of the Gatsby Remark Plugins. This is because I prefer to fix image CSS issues myself. There may be a better fix though.
When deploying Gatsby, assets need to be copied over.
"pre-deploy": "cp CNAME public; cp *.html public; cp README.md public && cp -rf ./assets ./public", "deploy": "npm run pre-deploy && gatsby build && gh-pages -d public --branch master",
pre-deploy makes sure that basic information that is not within the
/public folder is added so that images are available in