Vitepress based documentation #1061
Conversation
|
We need a proper support for MultiDocumenter before SciML can adopt vitepress |
|
Also buildkite deployment detection fails for reasons unknown, that's why we had added passing in the decision variable to Vitepress. See how Lux does it https://github.com/LuxDL/Lux.jl/blob/60c595ec9490dbdcce70c21ec4d577ef1d4f9165/docs/make.jl#L87-L88 |
Definitely, (or similar?). I just wanna to see if something could be broken. This is a huge use case. I will take a look at the deploy issue again. Thanks. |
|
Yes multidocumenter is essential. Notsure how this connects to it. |
|
It still isn't detecting the key. This is probably because buildkite disables forks from accessing secrets? |
|
apparently it builds without any issues. I will take this as a good sign 😄. The multidocumenter thing is not just a super navigator tab for all repos? |
|
Yeah it demonstrates it's viable. It just needs multidocumenter and key things. @thazhemadam can do the key things, but we should wait until there's a plan with multidocumenter @pfitzseb |
|
Closing as it is stale, but we are talking with @asinghvi17 about doing something to SciML hopefully down the line. I want to get SciML to vitepress but we need to think more about the whole multidocumenter setup and less about the single repos. |
|
MultiDocumenter 0.8 should somewhat support vitepress generated docs, at least visually. You will get two top-bars and potential keybinding conflicts though. |
let's see.