Anshul Singhvi
Anshul Singhvi
We could provide custom functions to the `make` kwarg in `deploydocs`: https://github.com/JuliaDocs/Documenter.jl/blob/a6f6c0c7e33f4b0c3fab38811ac691d646e2d46c/src/deploydocs.jl#L273-L276
Yeah I think Vitepress is not happy with the symlink. Will investigate...
This is purely caused by deploydocs afaict
I guess we can provide a fixer function in `deploydocs` like so: https://github.com/JuliaDocs/Documenter.jl/blob/a6f6c0c7e33f4b0c3fab38811ac691d646e2d46c/src/deploydocs.jl#L273-L276 which solves these problems? Not sure if that applies itself at the right time, though.
In which circumstances do you see this? I haven't been able to replicate on my setup (Google Chrome, MacOS) so far.
See also #70
I think that would be as simple as adding a JavaScript selector, since the structure of the folders is the same as what Documenter.jl usually generates (`dev, stable, v*, previews/PR*`).
The big issue here is that I need this to evaluate the items in `versions.js` at the root of `gh-pages`, preferably every time a client loads this. If there are...
https://stackoverflow.com/questions/39022630/how-to-display-an-array-to-a-html-sidebar-in-google-apps-script shows how to get a JS script done for Google Script but the outcome should be clear enough for Vitepress also. We might want to use either `nav-bar-content-after` or...
This now works, thanks to @lazarusA