5 ms·
And please remember to make good old server-rendered websites that can be archived by the Internet Archive.
by keewee7 5y ago
And please remember to make good old server-rendered websites that can be archived by the Internet Archive.
- capableweb 5y agoIn general I guess you can say that server-rendered websites are easier to assume they are archivable, but that doesn't mean a bit of client-side scripting will break the archiving process. If the scripts are also fetched (and not relying on 3rd party domains), the fetching and rendering process should work the same as long as the UI doesn't depend on API responses. Lightweight scripting, especially done within the <script> tags of the page, will work perfectly fine for most archiving software. Keep in mind all of them already fetch data from <img> tags, and most fetch 1st origin <script> src's as well.
- hansel_der 5y agoif your collection of letters and images is unviewable without some modifiying logic, you're doing it wrong.
- capableweb 5y agoAgreed! But just as client-side scripting doesn't mean "un-archivable", it also doesn't mean "require JS to be able to read/view content".
- hansel_der 5y agoagreed! client-side scripting should not mean "unreadable w/o", nevertheless it often does.
- capableweb 5y agoIf you're building SPAs, it usually does yeah. But I'm not sure how you went from "a bit of client-side scripting" and "Lightweight scripting" to "letters and images is unviewable without some modifiying logic" here in this thread? Sounds like you just want people to hear how much distaste you have for the dependence on JS for showing content?
- hansel_der 5y ago> Sounds like you just want people to hear how much distaste you have for the dependence on JS for showing content? i also want you to adopt and spread the pov, but yea.