3 ms·
Setting aside the “why stories?” part (plenty of people use UX stories — I do, though I am ambivalent about them), the powered by Vite line does have some conte
by dcre 3y ago
Setting aside the “why stories?” part (plenty of people use UX stories — I do, though I am ambivalent about them), the powered by Vite line does have some content to it:
1. If you’re already using Vite, you know it will integrate easily
2. If you’re not using Vite, if you know what Vite is, you at least know it’s fast and easy to configure
3. The fact that it’s made by a Vue core dev means it’s likely very good. There are a number of such “powered by Vite” tools with good reputations
- stevage 3y agoI'm surprised the integrating part matters. Does it matter if your internal documentation uses the same stack as your product?
- dcre 3y agoIt has to build the same stuff as the product because the examples are interactive. So being able to use your existing build config without doing anything special is great.