Where does Plenti sit in its rendering patterns for web apps? #257
-
Hi all, I ask this question as way to better understand this technology. I was watching this great video from Jeff Delaney on 10 Rendering Patterns for Web Apps this morning and thinking about Plenti. Which rendering patterns it uses...I think it should be his number 5. Static Site Generation with some Hydration ? I see that Plenti is now a Build-Time Render (BTR) Engine and also may be referred to as (“static”) rendering because it is precomputed server-side rendering. This article Theoretical foundations for server-side rendering and static-rendering although heavy in parts was helpful for me to further understand the different rendering patterns. Also interestingly I see that SvelteKit 1.0 was released recently which includes a lot of these rendering patterns. I think SvelteKit is like a backend framework that uses Svelte as its component framework. Below are the main Svetltekit features I could see:
Let me know what you think about any of the above. Cheers, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
We have aspects of several rendering strategies. Fundamentally Plenti creates static websites, but that's the fallback behavior because Plenti also automatically hydrates into an SPA. That's exactly the technique Jeff describes as server-side rendering with hydration, but the real differentiation is when this process happens. He's discussing the SSR taking place on each web request, in Plenti the SSR takes place at build time... and as I watch the video further I see he mentions SSG with hydration - this is exactly what we're doing. So you're 100% right @jamestagal, it's number 5.
That's just me trying to popularize a different way to describe these type of apps because I wasn't happy with the current terminology (because of course we need more acronyms 😂). Other existing terms for this are SSG and Jamstack, but IMO those do a poor job describing what differentiates these apps:
I haven't had a ton of time to play around with SvelteKit, but it's safe to bet it does a lot more than Plenti does. With SvelteKit you can choose among several different rending strategies vs with Plenti we are targeting one very specific way to build websites because we think it's the easiest and cheapest way possible to run these sort of apps. We basically want to bring super powers to frontend developers so they can design an interface and essentially get the backend / editing experience for free without having to rig it up themselves. |
Beta Was this translation helpful? Give feedback.
We have aspects of several rendering strategies. Fundamentally Plenti creates static websites, but that's the fallback behavior because Plenti also automatically hydrates into an SPA. That's exactly the technique Jeff describes as server-side rendering with hydration, but the real differentiation is when this process happens. He's discussing the SSR taking place on each web request, in Plenti the SSR takes place at build time... and as I watch the video further I see he mentions SSG with hydration - this is exactly what we're doing. So you're 100% right @jamestagal, it's number 5.
That's just me trying to popularize a different w…