feat(website): automatically publish latest blog posts to website

[Jaapiehetaapie]

This only fetches the posts at buildtime

[dantaik]

This is fine for now, but assuming this repository is stable enough and there is no requirement redeploy, then this solution will not work. I still prefer the dynamic loading approach.

[dantaik]

This is fine for now, but assuming this repository is stable enough and there is no requirement redeploy, then this solution will not work. I still prefer the dynamic loading approach.

[dantaik]

This is fine for now, but assuming this repository is stable enough and there is no requirement redeploy, then this solution will not work. I still prefer the dynamic loading approach.

[dantaik]

This is fine for now, but assuming this repository is stable enough and there is no requirement redeploy, then this solution will not work. I still prefer the dynamic loading approach.

[dantaik]

This only fetches the posts at buildtime

This is fine for now, but assuming this repository is stable enough and there is no requirement redeploy, then this solution will not work. I still prefer the dynamic loading approach.

[Jaapiehetaapie]

#13169 (comment)
It was mentioned here that fetching at build time would be the best option.

[dantaik]

#13169 (comment) It was mentioned here that fetching at build time would be the best option.

I see it differently.

BTW, have we already merged a PR of yours that automatically fetch the data in real time? It is in production, isn't it?

[wolfderechter]

BTW, have we already merged a PR of yours that automatically fetch the data in real time? It is in production, isn't it?

That PR was reverted with #13169 because of some issues

[Jaapiehetaapie]

I think this may be a good solution. But I think it's good to extract the 'on schedule' to a new workflow file and maybe it's needed to add some secret code to the api, otherwise everyone can call it.

[Jaapiehetaapie]

If using node it is needed to commit the changes to the repository. So I think it's better to go with the API way. We could also setup an vervel cron job, but I think it's better to have everything in GitHub actions. Thoughts?