adoptium / blog.adoptium.net Goto Github PK

Outline

• Introduction
• Goals & Metrics
• The Sickest Seven
• Other Takeaways
• Respins
• Summary

There are several tables in https://blog.adoptium.net/2022/08/a-summary-of-the-july-2022-retrospectives/ that are no longer rendering as asciidoc tables. I think they were originally upon publishing.

Will need to fix and check other posts as well.

Include a few notes on Community day, Adoptium panel and SBOM talk as well as links to the recorded material when it becomes available on the EF youtube channel

We are now ready to setup the DNS for the netlify app to point to blog.adoptium.net @chrisguindon please can you get this setup?

https://blog.adoptopenjdk.net/2021/08/goodbye-adoptopenjdk-hello-adoptium/ has a link labelled 'Adoptium API' which leads to a non-existent page: https://blog.adoptopenjdk.net/2021/08/goodbye-adoptopenjdk-hello-adoptium/api.adoptium.net.

Hello,

The Linter check of my recent PR #197 failed: https://github.com/adoptium/blog.adoptium.net/actions/runs/3457975148/jobs/5771930669

From the log, I think we need to bump the node version or lock the version of gatsby-cli in the workflow.

The 'Install Gatsby CLI' section shows the version of gatsby-cli is 5.0.0:

> [email protected] postinstall /opt/hostedtoolcache/node/14.20.1/x64/lib/node_modules/gatsby-cli
> node scripts/postinstall.js

According to the release note[1] of gatsby-cli 5.x, said users need to upgrade Node to 18.

Anyone can help this problem?

[1] https://www.gatsbyjs.com/docs/reference/release-notes/v5.0/

Switching from react-helmet to Gatsby Head API will require more work than changing the <SEO /> component. As explained in the reference guide you'll need to add a Head export to any page that should have that data (https://www.gatsbyjs.com/docs/reference/built-in-components/gatsby-head/).

We have a guide on a SEO component here: https://www.gatsbyjs.com/docs/how-to/adding-common-features/adding-seo-component

Right now you have your metadata inside the body: