[Feature] VitePress documentation and examples

[finetjul]

Motivation

VTK.js now relies on VitePress ! 🥳
There are some left-over improvements to make before cutting a major release.

Detailed Description

• Document instructions to build website locally. It's not clear in what order each command must be called.
• npm run docs:build should not erase examples built by npm run docs:build-examples
• Provide standalone examples with no "imports". (could be just for "Examples/Applications" examples)
• Provide un-transpiled examples (see Tweak vitepress examples #3418 (comment))
• npm run example is failing due to ./Documentation/config.js file missing

[finetjul]

npm run example is failing due to ./Documentation/config.js file missing

FYI @daker

[finetjul]

Provide standalone examples with no "imports". (could be just for "Examples/Applications" examples)

@daker this one is the last issue before we can cut the next "major" release. How hard is it ?

[daker]

I have already give it a shot but for some reason the rollup build was crashing, i will give it another try

[sudomakeinstall]

All--

FWIW, this sequence worked for me starting with a freshly cloned repo--I don't totally understand the build system though and got there through some trial and error, so not positive if it is optimal:

npm install
npm run build
npm run docs:generate-api
npm run docs:generate-examples
npm run docs:generate-sidebar
npm run docs:generate-gallery
npm run docs:build
npm run docs:build-examples

To use:

npm run test
npm run docs:serve

A few thoughts:

• Though doing this does allow me to build and serve the example page locally, it pollutes my local repo with numerous untracked ./Documentation/api/*.md files. Maybe some logic should be added to the .gitignore? Or maybe something wrong with my build sequence.
• Also, this sequence adds untracked changes to ./Documentation/.vitepress/sidebar.ts, which appears to be a blank file in the repo. Maybe this should be deleted from the repo and added to .gitignore? Or again maybe I've misunderstood something about the build.
• The last thing that would be very helpful would be to have clear instructions on which subset of commands need to be rerun in different situations.

It seems to me that if I only change a source file, I can just run:

npm run docs:build-examples

If I only add an example file, I can just run:

npm run docs:generate-examples
npm run docs:generate-sidebar
npm run docs:build
npm run docs:build-examples

And if I only add a test file, I don't seem to need to do anything. But again, this is mostly through trial and error so ideally this would be verified by someone who understands the build system better than I do.

Hope this is helpful to someone (including myself next time I try to build hah). As always, thanks so much to all the maintainers of this excellent library!

Best,

--Davis