Build completely new blog when Gatsby v5 released

[lonsagisawa]

Gatsby v5 REQUIRES node v18, but I can't resolve gatsbyjs/gatsby#35607 despite tried some workarounds like:

• forcing resolution source-map@next
• trying gatsby@next (gatsby v5 beta for now)

I don't want to stick to Gatsby v4 forever, and node v16 eventually going to EOL anyway, I decided to trash this code base and build from scratch.

Feature list / Ideas

• Pull articles from Contentful
  • What's modern best practice? Taking 2min to build seems not normal.
  • Why some images contained in container div element, some images not...
• Build on Gatsby Cloud, deploy to Vercel combination continues
• Stylesheets...
  • I found to hate sanitize.css, some elements drives me crazy. Make move to some more modern reset.
  • I'm only using styled components feature from Emotion right now. Maybe give styled-components try.
  • Going back to Tailwind is also an option.
• Sane, clean and modern development experience...
  • TypeScript first!
  • Make linters working(not working currently for some reason).
• Migrate syntax highlighting to PrismJS
  • PrismJS had some incompatibilities to CSS framework that I had used before Tailwind. It should be fine with my own style or Tailwind.
• Maybe drop RSS feed support.
• Heads up to some Gatsby v5 caveats!

[lonsagisawa]

Gatsby v5 released, and my work started.

• Found nicer way to inject CSS reset.
• Enabled TypeScript, ESLint and Prettier. Type safety gives me a lot of peace of mind, auto-forcing coding style sometimes annoying but helps improve code quality and consistency.
• Tried styled-components first, but back to Emotion.
  • Due to gatsby-plugin-image caveat.
• Maybe try slices? Low priority though.
• Contentful integration going to be later.

[lonsagisawa]

Done!