Modernise website technology stack

The current loopback.io website stack leverages Jekyll. Although it has, and continues to, meet our needs for hosting a simple website, there are certain issues which makes it unsustainable in the long-term:

1. Unfamiliarity of Ruby and Jekyll among the maintainers
2. Slow build times
3. Inability to use component-based, modern front-end development workflows
4. Legacy baggage

In alignment with the earlier blog modernisation effort, this issue is to track rewriting the current website in a modern, Node.js-based stack.

Currently, prototyping work is being done with Next.js.

Start by reviewing the current Jekyll-based website and the Next.js prototype mentioned in the issue. Compare the existing site needs with the proposed Node.js-based stack; done means the website has been rewritten in that stack, though the issue does not define a detailed migration scope or specific tests.

Written by the indexing model from the issue text.