4 ms·
things like: • we can't have any dynamic pages, everything has to be static HTML • we don't control the actual page; our job is to create a fragment of HTML t
by rich_harris 6y ago
things like:
• we can't have any dynamic pages, everything has to be static HTML
• we don't control the actual page; our job is to create a fragment of HTML that the CMS stitches into the body, then associate that fragment with some publish metadata...
• ...but during development, we need a simulacra of the NYT article template
• we have to be able to create AMP versions of almost every page
• our old app was already fairly Svelte-centric, and we wanted to reuse as much as possible
• we wanted to use client-side navigation to avoid page reloads (while capturing custom navigation analytics) e.g. because it makes no sense to make people load MapboxGL repeatedly
It's possible that we could have coaxed one of the existing static site generators into fulfilling all these requirements, but it seemed like we'd be in uncharted territory without the benefit of having the SSG maintainer on staff!
- searchableguy 6y agoAre there any plans to support deno?
- rich_harris 6y agoNot concrete plans but I expect it will happen, yes (at the very least in the sense of having an `adapter-deno` to allow the built app to run in Deno; running SvelteKit _itself_ in Deno is a separate issue)
- searchableguy 6y agoYeah, that will require rewriting lot of code for development so I understand. Just curious, are you aware of few of the spinoffs of svelte for deno like snel? https://github.com/crewdevio/Snel https://github.com/crewdevio/Snel Have you used deno for any toy projects and how did you like it? Any wishes or criticism?
- borsemayur2 6y agoI just tried snel. It works pretty well. I'm looking forward to use it for my upcoming book on Deno.
- borsemayur2 6y agoAleph.js (Deno alternative for Next.js) is worth trying. Though, Deno and Aleph.js are still in early phases for production use.