Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TODO: Add frontend framework (which one?) #5

Open
nberlette opened this issue Jan 28, 2022 · 0 comments
Open

TODO: Add frontend framework (which one?) #5

nberlette opened this issue Jan 28, 2022 · 0 comments
Assignees
Labels
enhancement New feature or request good first issue Good for newcomers poll Cast a vote and help guide the project trajectory!
Milestone

Comments

@nberlette
Copy link
Owner

nberlette commented Jan 28, 2022

// TODO: add a frontend framework, current factoring has outgrown itself (poll) 

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?

Next.js (React)
Nuxt.js (Vue.js)
SvelteKit (Svelte)
Nothing, keep it ugly and broken like it is now.

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!

@nberlette nberlette added enhancement New feature or request good first issue Good for newcomers labels Jan 28, 2022
@nberlette nberlette self-assigned this Jan 28, 2022
@nberlette nberlette changed the title Move to Next.js or SvelteKit; frontend has outgrown this factoring Add a frontend framework, current factoring has outgrown itself. (poll) Jan 28, 2022
@nberlette nberlette added help wanted Extra attention is needed poll Cast a vote and help guide the project trajectory! labels Jan 28, 2022
@nberlette nberlette added this to the Frontend Framework milestone Jan 28, 2022
@nberlette nberlette removed the help wanted Extra attention is needed label Jan 28, 2022
@nberlette nberlette changed the title Add a frontend framework, current factoring has outgrown itself. (poll) TODO: add a frontend framework, current factoring has outgrown itself (poll) Jan 28, 2022
@nberlette nberlette pinned this issue Jan 28, 2022
@nberlette nberlette changed the title TODO: add a frontend framework, current factoring has outgrown itself (poll) TODO: Add frontend framework (which one?) Feb 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers poll Cast a vote and help guide the project trajectory!
Projects
None yet
Development

No branches or pull requests

1 participant