A. Write it down sufficiently succinctly to publish in academic journals. Or failing that, a book with an ISBN that gets archived in libraries. Perhaps creative commons etc licencing will help a bit, but it's gotta make it to distributed archives.

B. Teach a future generation. It lives through them and gets built on.

C. Embed it in what you do. It might not be a webpage, but there's code and ideas living in organisations today that have outlived their authors.

In this sense, perhaps bash.org hasn't died. It's just outlived its domain.