What's Next for SvelteKit Omakase? 🚀

[n00ki]

Hi there, my fellow builders 💪

As I continue to brainstorm ways to enhance SvelteKit Omakase, I realized something crucial: I can't do it alone! Your insights and feedback are invaluable to the evolution of this project.

Originally started as my personal boilerplate, it is now has grown into a tool that I believe can truly benefit many web developers. While it already provides significant value by saving time and effort when creating new SvelteKit projects, there's always room for improvement.

"Unless someone like you cares a whole awful lot, nothing is going to get better. It's not."
— Dr. Seuss

So, I'm reaching out to you, the community, to help shape the future of SvelteKit Omakase.
What features or enhancements would make this starter project even more useful for you?
Here are a few ideas to get the discussion started:

• Command Line Interface (CLI): Would a dedicated CLI streamline your workflow?
• Multi-Database Support: Should we support more databases or different configurations?
• Email Providers: Should we support multiple email providers out-of-the-box?
• Internationalization (i18n): Is i18n something you need for your projects?
• Onboarding & Documentation: Should we focus on improving the onboarding process with elaborate annotations and guides?
• Testing: How important is end-to-end (E2E) and unit testing for your development process?
• Other Features: Are there any tools or features you think are missing or need improvement?

Your feedback is crucial in ensuring SvelteKit Omakase continues to meet the needs of developers.
Please share your thoughts and suggestions!

Looking forward to hearing from you all.

Cheers,
Noam