TODO: Add frontend framework (which one?) #5
Labels
enhancement
New feature or request
good first issue
Good for newcomers
poll
Cast a vote and help guide the project trajectory!
Milestone
I'd really like to hear your input on this: which frontend framework do you think provides the best solution for the icns.ml project, and (more importantly) the needs of its users?
Background
As you can clearly see in
api/index.ts
(38e5d36), the current frontend factoring is just hideous:https://github.com/nberlette/icns/blob/38e5d36b5bfcb1dfae61250b7845ef95c3eeb832/api/index.ts#L30-L40
While this format of a no-framework API ("Other" in the Vercel project configuration) initially seemed to work alright, it was never intended to support anything beyond a static HTML-rendered version of the
readme.md
file.As the frontend's functionality (and thereby its footprint) expands, I think it's pretty clear we've outgrown our outfit here 😅
Potential Solutions
When it comes to frameworks, lately I've been pretty hooked (no pun, I swear) on Next.js and SvelteKit, which are now *both being developed by Vercel. Since SvelteKit is still in it's pre-1.0 public beta, and lately they've pushed some completely breaking changes, I continue to find myself erring towards Next for production-grade dependability.
The choice is yours
I don't expect my little cobweb-filled corner of GitHub to get very much traffic, so the impact your vote will have on icns.ml's future is pretty significant. Thank you!
The text was updated successfully, but these errors were encountered: