-
Notifications
You must be signed in to change notification settings - Fork 102
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
I did a thing: reimplemented pronoun.is in svelte #149
Comments
Super cool @lucasew ! Really smart to port to something that is static and a lot easier to host. |
unfortunately this is a misunderstanding about how pronoun island worked. it was not static at all. this for example doesn't work: https://svelte-pronounisland.vercel.app/byte/byte/bytes/bytes/byteself while on the original pronoun island it did work, if you gave it all 5 pronoun conjugations of a pronoun it did not have in its database, it would still display those properly. this requires a dynamic page. from an archived copy of pronoun island:
|
Good catch. If length of the route is 5 then handle it as each word as a part. Edit: just implemented and deployed the fix. |
As issues like #147 say, this site is down. I guess that it is because of the heroku rugpull.
Analyzing the scope of the project, that looked like something that could be done with a more static approach. The backend just crunches some data and doesn't store state, and the stuff it serves can be trivially processed on the frontend.
For the remake I choose to do with SvelteKit, it's a very cool tech, very straightforward to learn and iterate and has a routing scheme as powerful as frameworks like Next.js have.
I did it this night, it took a few hours, maybe less if not counting the procrastination, but here it is.
The repo is in my GitHub and I hosted that on my vercel account for free.
There are some polishing that I didn't work on yet, like the favicon and the SEO tags, but that shouldn't take much time.
I stole the CSS, so the site will look like a clone.
The text was updated successfully, but these errors were encountered: