> The key is not to use any code that won't be supported in 40 years. So that means no databases.
A database could help resolve your search problems. Postgres has been around in some form for over 40 years and has never been as popular as it has been now. It has a good shot of still being around and runnable in some form in 40 years, I think. It has full text search, and even trigrams for fuzzy search.
Yes I've thought a bit more about this topic and am actually writing up a response to my own post - Database are probably ok if you take a raw .sql backup; which is essentially plain text, or at least will be viewable in some form in the future.
https://sqlite.org/ "The SQLite file format is stable, cross-platform, and backwards compatible and the developers pledge to keep it that way through the year 2050." Doubt you can do better than that.
Half a decade ago, I picked Hugo as the SSG and so far it has held up[1] the test of time. To me, content is far more important than website design. While it’s not forbidden to go overboard with JS and CSS frameworks, I've found that people who do rarely offer content I can really learn from.
A database could help resolve your search problems. Postgres has been around in some form for over 40 years and has never been as popular as it has been now. It has a good shot of still being around and runnable in some form in 40 years, I think. It has full text search, and even trigrams for fuzzy search.