V1 Release ⭐
Once the https://github.com/vikejs/vike/labels/v1%20release%20%3Astar2%3A tickets are implemented, Vike can be considered a feature complete, highly polished, and robust tool to build modern apps.
Plan:
- [x] Rename vite-plugin-ssr to Vike.
- [x] Stable release of the https://github.com/brillout/vite-plugin-ssr/issues/578 (and soft-deprecate old design).
- [ ] Implement https://github.com/vikejs/vike/labels/v1%20release%20%3Astar2%3A tickets.
- [x] Rehaul marketing pages to target a wider audience with a more professional/dry tone. (The current copy has more of a personal/hobbyist/passionate tone.) Also make
vike.devprettier. - [ ] Marketing, marketing, and marketing. (Lots of comments and blog posts on social news sites, reach out to news sites & influencers, automatically track relevant news, ...)
Is v1 okay?
@BlackCubeNo99 Yes the v1 roadmap is still the plan. (Althoug the Vike rename may happen earlier than planned.)
I just commented here to see the day Vike released v1 - To see your sweet of your efforts in a long time! Thank you!
Rehaul marketing pages to target a wider audience with a more professional/dry tone. (The current copy has more of a personal/hobbyist/passionate tone.)
Please don’t. :) Professional/dry tone is very uninspiring, and the marketing pages are very detailed now, just like developers like it.
I do intend to keep a unique touch to Vike's copy (e.g. I'll probably keep the part about us being passionate), but I do think that a professional/dry tone is paramount for gaining trust: we're serious about what we do and I want to communicate that.
- Why use "+Page" instead of "index"?
- Why use uppercase letters instead of lowercase (HTTP routes are case-insensitive)?
ETA: end of this summer.
[!NOTE]
1.0.0is just a number really: Vike is very much already production ready and used in mission-critical production apps. (Many/most others projects would have already released1.0.0a long time ago.)