Claudio Wunder

Bump, just to figure things out, are there any other items that would need to be done for the calendar after this gets merged? (Eg.: description, CSS changes such as...

Hmmm! Interesting, doesn’t Gatsby supports APIs and is able to cache them? We could basically create an API endpoint that already maps the data that Frontend needs in the way...

@benhalverson should we create issues for these: ``` A few ideas to fix this is Setup a proxy API with a serverless function Setup an express server as a proxy...

@benhalverson, I believe there are some dependencies resolution having issues there, could you re-checkout your `package-lock.json` file from `main` and re-run npm install?

@benhalverson also regarding [this](https://github.com/nodejs/nodejs.dev/pull/1713#issuecomment-909446661) comment. Are those design changes incorporated into this PR? Also, @joesepi commented on the original PR regarding some style changes [here](https://github.com/nodejs/nodejs.dev/pull/1713#pullrequestreview-742725413) do you believe you would...

Something feels wrong with the rebase, it's saying this PR has 90 commits? Maybe you should squash the original calendar commits of this PR and drop all the other commits,...

Yeah, but still @benhalverson it looks like on the commits tab, the whole history is still here... If you want, I could try to fix the tree of this branch...

And also regarding the `peerDependencies` conflict, you can use the `overrides` option of `package.json`. Something like: ```json { .... "overrides": { "react-big-calendar": { "react": "$react" } } } ```

@benhalverson do you know if the `i18n` module is functional/maintained. Should we rely on it? Or should we proceed with the YAML approach we were talking about?

Hey @zeke @JohnTitor is there any chance the `nodejs/i18n` package could also provide the data in JSON besides just Markdown? (https://github.com/nodejs/i18n/issues/689)