vocal blade
My team have been on a two-year long slog to rebuild https://gamepress.gg/ and create a modern wiki engine from the ground up.
We eventually hit a wall with Nextjs, and in June took the gamble to completely rewritten the codebase in Remix.
The gamble paid off!
Happy to finally launch the first gaming wiki (of many!) on the Nalu platform:
Deployed App: https://nalu.wiki
Github: eventually
Ryan's "every routes being their own API route" tweet https://twitter.com/ryanflorence/status/1530652753839566848 was an huge inspiration for the move, and the missing piece to make the whole modern wiki stack work.
It's the underlying tech that powers our frontend MDX-based text editor! https://nalu.wiki/p/new?template=30&nalu=toweroffantasy
hasty wren
My team have been on a two-year long slog to rebuild <https://gamepress.gg/> and...
What was the "wall" that you hit with Next.js?
vocal blade
Early on we thought SSG was a great idea - serving static pages makes perfect sense for a wiki, right? Until we approached rebuilding 30k pages on each compile and builds began to timeout (Render.com has a 30 minute build limit).
We were hoping that on-demand ISR would be our savior, but when it finally came out, Vercel basically vendor locked the feature that really mattered to us - persist cache documents between deployments.
vocal blade
Hosting on Vercel would be too expensive, considering GamePress sees >100TB in traffic monthly.
vocal blade
I enjoyed Next and its very helpful community, but it wasn't a good product fit for what we're trying to build.
eternal umbra
Looks awesome! 😄
We also have a site with a lot of pages and ended up moving from Next to Remix. 🙂
@vocal blade how did you approach login and HTTP caching?
vocal blade
I'm more of a frontend person, so when @livid cedar is around he can probably answer it better.
Clerk.dev for auth atm, was part of the stack that carried over from the nextjs build, might look into bringing auth inhouse though considering how easy Remix makes it. https://www.youtube.com/watch?v=OK-AGnsOo5U&list=PLV5CVI1eNcJgNqzNwcs4UKrlJdhfDjshf&index=2
We have Cloudflare out front for caching.
merry nebula
I enjoyed Next and its very helpful community, but it wasn't a good product fit ...
woah 🔥 🔥
you should WRITE AN ARTICLE ABOUT THIS
this is a gem, and can help many others consider remix over next.js
livid cedar
We use Cloudflare page rules to disable caching if an auth token is set, otherwise we always cache the document for anon users. Planning on setting up redis to improve api performance for logged in users.
vocal blade
this is a gem, and can help many others consider remix over next.js
Oh definitely! I plan writing a series about our Remix migration experience, once I figured out why the MDX editor would randomly crash!
merry nebula
Oh definitely! I plan writing a series about our Remix migration experience, onc...
sounds awesome
i might start using a bit of nalu
im vibing with the theme and stuff
obv am an anime fan 💀
merry nebula
unkempt hedge
Please blog about this!
shut dew
@vocal blade awesome 🔥
But when I click on a route, it takes time to load it and it's confusing the link was clicked or not. Maybe add a progress bar for page transition?
NProgress is a neat
https://ricostacruz.com/nprogress/