
WORKING ON A WILD @eleventy IDEA TODAY
IT IS WILD
started with 110 errors in the refactor, down to 66 now…
WORKING ON A WILD @eleventy IDEA TODAY
IT IS WILD
started with 110 errors in the refactor, down to 66 now…
Alright, so the previous demo was a generic Eleventy project in the browser — by itself a big milestone.
Here’s another big milestone: loading code directly from the `eleventy-base-blog` GitHub repo and using Eleventy to `innerHTML` the generated result directly to the browser. The Eleventy build takes about ~200ms in-browser and uses the RSS, Syntax Highlighter, Image, and Navigation plugins.
Still a few rough edges but we’re making progress.
(for the record, the use cases here are limited — and should be limited — please JavaScript responsibly)
@zachleat git branch next-js-integration
@nathanbottomley rm -rf .git
@zachleat @eleventy This predates you, but trust me that it's apt.
https://www.youtube.com/watch?v=ZhPFsLAmShY
@zachleat is this what I think it is
@danleatherman it’s a rorschach test
@zachleat FINALLY! I can client side render my blog like all the cool kids!
@matt HYDRATION ERROR
@zachleat
I'm doing this right, right?
eleventyConfig.addTemplate("index.md", "<blog-app></blog-app><script src='./blog-app-bundle-34daef.js'></script>")
@matt *eyes narrow*
@zachleat 🤔🤔🤔
@zachleat Cool vs. Insane. Why choose?
@zachleat brb putting this inside my react component.
@mayank how dare you
@zachleat what in the sweet goddamn
@ardouglass this is karen behavior andrew!!
@drumsensei it’s only a mistake if you use it wrong… wait
@zachleat your secret is safe with me Zach 🤐
@zachleat This is incredibly weird. I love it!
@zachleat Finally, 11ty SPAs!
@timsev these are fighting words
@zachleat First time a screenshot has this huge impact on my plans ! Thanks !
@eQRoeil well now you have to reveal your plans
@zachleat I need to build a website with a lot of pages (thousands). I do not want to rebuild the entire site each time an update is needed on 1 page (regularly 1 or few pages will need an update). So the plans were to **start** with 11ty, keep a limited compatibility for site wide changes and dev a solution that allow to make edits from a dedicated app that can produce the same output.
11ty running in the browser will remove or simplify some of the challenges.
@zachleat I also think it will be easier to make previews and offer alternatives to git based CMS / workflows.
@eQRoeil I don’t think you’ll want to build clientside as the user experience for end users (unless I’m misunderstanding) but the rest of it makes a lot of sense!
@zachleat not building clientside for end user (I'd take the lambda / serverless functions route or use Nuxt)
Only on the "edit app" part
@zachleat slowly put down the keyboard...
@erikKroes ahahahahahahahaha web performance zach is dead
long live SPA zach
@zachleat oh my oh my
@derhaug (this is a joke of course, not doing the SPA thing here)
@erikKroes @zachleat So many ideas already ..
@zachleat ☠️
@matuzo ⚰️
@zachleat 👀👀👀
@zachleat ironically, I’m excited about the serverless possibilities this potentially unlocks on non-node runtimes (if I’m understanding the screenshot correctly!) any chance this capability extend through to webc as well?
@d3v1an7 what runtimes specifically? I’m aiming for all core plugins to be supported yeah
@zachleat oh heck, that'll be so good! we moved most of our workloads away from netlify over to cloudflare, but the webc cms-preview had to stay on netlify serverless, as i couldn't get it running on the worker runtime (workerd) -- mainly issues with filesystem stuff.
@zachleat sorcery (good)
@zachleat •extremely doctor ian malcolm voice•
your scientists were so preoccupied—
@zachleat I’ve been tinkering with something similar (running a SSG in the browser), what’s your goal here?
@mb21 I probably won’t reveal the ultimate goal (yet!)
@zachleat so freaking awesome