3 ms·
Sure, but you also have to manually redownload the entire site whenever there is a change.
by paxys 6y ago
Sure, but you also have to manually redownload the entire site whenever there is a change.
- leephillips 6y agoThat’s what rsync is for.
- jolmg 6y agoor wget, since rsync doesn't work with HTTP.
- leephillips 6y agoI was thinking (assuming this is one's own stuff), use rsync to download the files to avoid transferring lots of unchanged stuff. But if this is for an end user, yes, there would only be html access.
- frenchyatwork 6y agoYou would with a SPA as well. Edit: incidentally, a common way for this to work is that the documentation just comes with the software itself, so it's just sitting there on you computer. If the software updates, the documentation updates.
- TheGoodBarn 6y agoTo a degree though, thats where PWAs come in. Websites like https://devdocs.io/ https://devdocs.io/ do this exact thing through desktop Progressive Web Apps. Basically you keep your markup & source as static as possible, and allow a serviceWorker to cache those files locally. This can also be done with a SPA, but if we're talking docs, you get the benefit of only having to update a specific page if its raw html.
- imtringued 6y agoDocumentation doesn't change in real time.
- ogre_codes 6y ago> Documentation doesn't change in real time. If you are a javascript developer chasing the bleeding edge of web dev, it's pretty close to real time!