Announce node 24 is now the default Node.js version

[pacostas]

Merge after

There is a nodejs release buildpack with the PR from node-engine in it.

• Setting node 24 as default node version node-engine#1434

Summary

This PR:

• Fixes hugo command to run locally hugo server -D
• Minor fix on the stacks article, as the title ends up showing two times instead of one
• Fixing my photo to appear on the blogpost by renaming the pacostas.jpeg to pacostas.jpg
• Adding the blog post that announces that nodejs 24 is the default node version

Use Cases

Checklist

• I have viewed, signed, and submitted the Contributor License Agreement.
• I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
• I have added an integration test, if necessary.
• I have reviewed the styleguide for guidance on my code quality.
• I'm happy with the commit history on this PR (I have rebased/squashed as needed).

[anthonydahanne]

what is it for?

[pacostas]

Running hugo locally with command hugo server -D , it fails due to resources.ToCSS has been deprecated from 0.128 version, based on their documentation https://gohugo.io/functions/resources/tocss/#article instead we should use css.Sass as it says. Practically, this is something internal that hugo uses, and it does not affect the outcome of the website.

[dmikusa]

We are quite a few versions behind, https://github.com/paketo-buildpacks/blog/blob/main/.github/workflows/deploy.yml#L27. Not sure if this is supported in the old version too? That would be my only concern making this change.

You might want to omit this for now. We should do a dedicated PR to udpate Hugo.

[pacostas]

Ooops, you are right. Ok, I removed the commit.

[pacostas]

I guess, we would like to have something similar to what we do with jam and pack and in general with all the tools. Like a tools.json file with the version and a bash script that will do the installation locally and will also be used on the github action. That way is also going to be easier to update as we can have an action for doing that, similar to what we do with all the tools. The problem though is still the review process, as we can not be 100% that nothing breaks on the rendering side, in terms of styling etc. but having an installation script, definetely will make the review much easier as it will be easier to install and test it locally

[dmikusa]

Yes, that would be a great improvement for running this locally. I have the same issue that I think you're hitting. I install hugo on my own, which means I get the latest, and that's not always aligned with the project. I'll open an issue.

[anthonydahanne]

@pacostas I noticed and suggested changes to 2 typos : throught -> through and take at look on -> take a look at but even though those suggestions were closed, the typos are still here? Is it on purpose?

[pacostas]

@anthonydahanne Oops, you are right, I force pushed and accidentally overridden the typos, I added them 116ef53 Can you also approve and merge the PR? New default nodejs has been also pushed to the builders so we can announce it now.