Porting to a different stack

[razzeee]

Hey @jimmac @allanday @AsciiWolf @mwleeds

I'm currently consider to redo this page with next.js mostly to be able to share components from flathub - but also to get this to a more modern stack, that maybe more (webpeople) can help with.

Please let me know, if that's a direction that's fine with you

[AsciiWolf]

It sounds like a good idea to me.

You could probably try asking @barthalion to give you push rights (Collaborator status) to this repo.

[barthalion]

Just keep in mind this is currently a static website so if we switch to next.js it has to work with next export.

[razzeee]

yes, that would be my plan - should hopefully be easier here

[jimmac]

Personally I don't think flatpak.org is a web app. Even Jekyll can make you waste an hour on dependencies when you come back to a project after a few months to do a 3 line CSS fix.

Tobias changed my mind about using plain HTML+CSS for a website. It really works best long term in terms of maintenance. Short term convenience is really diminished by dependency cost.

I have no experience with next.js though, it might be just fine.

[razzeee]

Tobias changed my mind about using plain HTML+CSS for a website. It really works best long term in terms of maintenance. Short term convenience is really diminished by dependency cost.

While it should be maintainable, I don't think we should optimize for that, we should optimize for users and people being able to find it.