Add Vite + Vike "Getting Started" docs

[ambergristle]

• wanted to get docs on all the vite plugins in one place
  • will also serve as foundation for additional context + examples in the future
• not totally sure "Getting Started" is the right place for Vite, but i didn't include any examples
• i'm still a little hazy on what the current recommended setup for Hono + Vite is
• am working with Vike team to get some Vike + Hono patterns documented

[ambergristle]

@yusukebe @MathurAditya724 it's been brought to my attention that there's a conversation about whether integration/tooling docs belong on the hono docs website. i wasn't able to find a public discussion on the topic, but i wanted to share a few thoughts. please let me know if you'd like me to move this conversation elsewhere.

this is a question we considered when creating the honc docs. in that case, we concluded that:

• part of what makes hono docs helpful is that they're simple, stable, and to-the-point
  • hono is too flexible a framework to effectively cover common use-cases without creating a lot of noise
• maintaining any third-party-specific docs is ultimately burdensome on the hono team
  • that's a lot of projects/api updates to keep track of, and external dependencies to understand

that being said, i think we'd agree that it would be valuable to develop the knowledge base for the hono ecosystem, and have some framework for collaborating with third-party teams.

blog posts and other technical content are part of the solution. i've started writing how-tos and in-depth articles on how to solve common project requirements with hono. if there are any topics you'd like to see covered, i welcome any suggestions. i wonder if there's a way to encourage more devs to create content though.

the best answer for third-party docs may be to leave that to them. instead of having examples/setup documents, the hono website could have an "ecosystem/integrations" page that just lists out available options with a short description + links out to the relevant docs. maybe even as a table. could be a good way for hono users to compare options for different components of their stack.

in any case, i have a lot of thoughts on the subject, but i'm eager to contribute however is helpful.