What a clever naming scheme! Nobody reads stories or books anymore, so when they see the word “story” they’ll automatically assume you mean UX Story! This isn’t ridiculously confusing at all.
What a clever naming scheme! Nobody reads stories or books anymore, so when they see the word “story” they’ll automatically assume you mean UX Story! This isn’t ridiculously confusing at all.
And to be clear when I say write I mean like a novel or blog post. Like with the English language.
Overloading is fine. Ambiguous use of an overloaded term is not. What is one to think of when they see words like "write", "stories", and God forbid, "book"?
Storybook stories, of course.
At most you can critique the HN headline drawing in randoms, which is a legitimate complaint, but I don’t see a problem with their copy especially for a brand new OSS project. Marketing sites are usually an after thought that improve after the first year.
Unless, you know, you think this new volunteer project should be selling you on using well documented component libraries or something.
Sarcasm aside, I actually do like Vite quite a bit. And I still think my main point stands that a framework that exists to document components co-opting the word “book” is ridiculous.
Even the use of french. Why French? Because it's really so exotic?