The Internet Archive has a new book: VANISHING CULTURE. (Digital copy is free.)
According to a Pew Research Center report, 26% of pages from 2013-2023 are no longer accessible. But that’s not the whole story. In a new study published in Internet Archive’s book, VANISHING CULTURE, data scientists working with the Wayback Machine have found: 16% have been restored through the Wayback Machine. 56% are preserved before they disappear.
A quarter of pages from the last slightly-more-than-a-decade gone. I guess that’s about what I would have guessed. I don’t love it, but it seems like the level of URL rot that just happens on the web. Maybe even feels a little low? 😬. Kinda cool the Internet Archive saves about half of it.

This resonated a little extra this week as a local mountain biking trail resource said they were closing:

When I see stuff like this, my brain thinks: OK fine, thanks for letting us know. But, like, you’re not going to just turn off the site, right?! No, they are:
Will The BendTrails Website Be Taken Offline?
We’re open to the possibility of a community group, business, or individual acquiring BendTrails’ assets and keeping the site online — but if that doesn’t happen, the site will be going dark on June 1st.
They want something like 80-90 grand for it. Which is fine. They worked on it for a long time and did a great job. I imagine it incurred costs, likely above and beyond what sponsors covered. Maybe they’ll get it, maybe they won’t.
I just can’t wrap my mind around “going dark”. It’s a WordPress site. Bluehost can host that for $3.99 a month ($9.99/month after three years). Not to trivialize money but that seems pretty doable and preferable to just shutting the thing off.
Maybe it’s a mental space thing though. I’ve had to walk away from projects by drawing pretty hard lines. If the website is still online, maybe it will still occupy mental space that they just can’t afford. You probably know I’m a fan of WordPress, but I’ll admit WordPress adds some additional mental overhead. There would be some prep like turning off any interactive features. Then somebody has to be in charge of updates forever, because WordPress is PHP and MySQL and such which will be subject to potential vulnerabilities forever.
A fella I know put together Bend Bike Rides in the wake of this. A burgeoning replacement. I don’t know the tech stack but I know the guy well enough I’m quite sure it’s not WordPress. Looks like static output (if JavaScript-y). If he needs to walk away from this site someday, there is options like Netlify’s “free forever” plan that feels a lot more likely to be able to be left forever with no mental overhead.
I’m just thinking about what the options are and what feels right when people need to walk away from a site. It’s nice the Internet Archive saves them, most of the time. But is that good enough? Maybe we just shouldn’t worry about it because they will take care of it? If we don’t think that’s good enough, what then? Should there be better tooling for static-izing a site and putting it somewhere inexpensive to live as a viewable time capsule?
For WordPress sites, there is a premium version of legacy. $38,000 will keep the lights on essentially forever. Many scoff, but I think it’s cool. I may not have pulled the trigger if it was my money, but I did happily use the service for my friend in kind.
Honestly I hope CodePen is an option for some situations and that we can evolve to make it an even better option over time. We’ve got deployment. It’s not free, but it’s not heavily limited either. The trick is getting a site to be entirely static, and I feel like there could/should be better tools for converting sites into this state.
The way I’ve handled this a few times (like you mentioned) is to get the posts out of WordPress and into a basic static site. You can grab something like Simple.css or Water.css and make a static archive that’s free or almost free to host.
In these cases, I didn’t prioritize retaining the design or layout, just the content. But I think that depends on the project you are archiving.
Example using Water:
https://able-dev.com/
Example using Simple.css:
https://blakewatson.com/ihs/
If you are really archiving a site and removing server side functionality, wget (https://www.gnu.org/software/wget/) is a great cli tool to make that happen. The tool will process any website as long as it behaves like a standard website. It can convert all pages to html, download external resources and convert internal links to relative urls so you can move an entire site as a package.
The command to generate a site as a self contained package would be:
wget -r -l 0 -p -k https://bendtrails.org/
Then you can take the website package and host it on any static host (many are free).
All that being said, bendtrails.org relies on Google Maps for some of their functionality which can get pretty pricy and may be some of the reasoning to close it down.
P.S. The zero in this font is ridiculous o vs 0?
I’ve tried to do some digital preservation of old projects, especially WordPress-based. As others have mentioned, I have generated static-site from the WordPress project, which is much more portable and easier to maintain.
I’ve done this using Snap, by Remy – https://github.com/remy/snap