RFC: A sharp samples remover

[eric-burel]

Goal

Vulcan is a big framework. We want to include a lot of features for you to get started.
But sometimes, you need something simpler. Maybe you don't need MDX to write your doc, or you only want to keep the server. You may prefer a CSS solution to Material UI.

What's more annoying in a starter than needing to remove all the default samples?

We need to include a few code examples in Vulcan Next Starter, to demo features but also to be able to test that everything is ok.

Ideas

• Isolate code samples, demos, and framework related stuff in folders named vn. The packages folder also isolates features.
• Write a script that eject from Vulcan Next, to get a clean start.
• Write scripts to remove specific features. UI libs like Material UI are a first good example
• Put configs into .vn: even if you don't remove them, they are isolated and easier to locate and update

Getting rid of Material UI

Material UI is an opinionated choice, but we should at least be able to document where it impacts the app even if you want to use only some components

• Material UI setups a default, global theme => remove the CSSBaseline component will remove styling of body