Update or replace with a rendered static page?

[lonnen]

This hasn't been updated meaningfully in 4 years and I thought I'd try to get it to build again, if only to update in-place on Heroku before #18 closes.

After updating package.json to a supported version of node I checked the dependencies and most are either abandoned, deprecated, or multiple backwards-incompatible updates behind.

I spent a couple minutes trying to update to a supported node, remove neutrino, and replace it with classic webpack. It's not operational, but I am publishing the work here:

main...lonnen:taskcluster-net:2023-update

It's tedious work, especially for what appears to be a single static page that links to the docs. Is this work worth doing, or should we just wget the existing site and call it a day?

[djmitche]

I'd say a single static page would be fine! I'm not sure anyone else is following this repo :)

[lotas]

Ohhh.. I thought I created ticket.. I saw this issue last year with building landing page and also thought it might be easier to simply replace it with the static page.
thanks @lonnen for the updates, getting rid of neutrino was necessary anyways if we plan to udpate it in future.

Maybe for now we can simply save index.html in build/ folder but keep the rest with your changes, just in case we'd need to update something?

Upd: Ticket was indeed created, but in JIRA: https://mozilla-hub.atlassian.net/browse/SE-3702
upd2: done in https://mozilla-hub.atlassian.net/browse/SE-4043