You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The generated HTML/JS/CSS from the documentation builds depend on cdnjs and Google Fonts right now. It might be useful in some cases to build the docs without CDN-ed dependencies.
Something also worth considering is that we are kinda vulnerable to a CDN going offline or becoming inaccessible right now. So we could also consider bundling by default.
The text was updated successfully, but these errors were encountered:
Couldn't agree more. I usually work under an unstable network, and the equations and fonts usually load very slowly :(
I think the LocalHTML is a better plan because it not only gets rid of online resources but also ensures that the page looks the same as the version it is built.
Hi, thanks for opening this. I think I'll need that feature too. :]
Some extra reasons why bundling the javascripts together with the doc would be marvelous:
Serving documentation that links to CDNs may require a GDPR banner in EU. This problem might get softened a bit by at least using the proper referrer policy in the generated HTML, there's currently none. (IANAL tho.)
Deployment of non-public (e.g., company-local) documentation doesn't leak user access stats and internal referer URLs
people who like to block javascripts don't need to unblock the whole cloudflare in order to get the doc search running
The generated HTML/JS/CSS from the documentation builds depend on cdnjs and Google Fonts right now. It might be useful in some cases to build the docs without CDN-ed dependencies.
Something also worth considering is that we are kinda vulnerable to a CDN going offline or becoming inaccessible right now. So we could also consider bundling by default.
The text was updated successfully, but these errors were encountered: