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:
Unfamiliarity of Ruby and Jekyll among the maintainers
Slow build times
Inability to use component-based, modern front-end development workflows
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.
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:
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.