51 replies

1. dan leatherman 4 min later

   @zachleat is this what I think it is

   1. Zach Leatherman 2 days later

      @danleatherman it’s a rorschach test

2. Rob Anderson 5 min later

   @zachleat love it

3. Matthew Mone 9 min later

   @zachleat FINALLY! I can client side render my blog like all the cool kids!

   1. Zach Leatherman 2 days later

      @matt HYDRATION ERROR

      1. Matthew Mone 2 days later

         @zachleat
         I'm doing this right, right?

         eleventyConfig.addTemplate("index.md", "<blog-app></blog-app><script src='./blog-app-bundle-34daef.js'></script>")

         1. Zach Leatherman 2 days later

            @matt *eyes narrow*

4. Khalid ⚡ 12 min later

   @zachleat

5. cthos 🐱 15 min later

   @zachleat 🤔🤔🤔

6. Paul Everitt 21 min later

   @zachleat Cool vs. Insane. Why choose?

7. Jason Garber 39 min later

   @zachleat what in the sweet goddamn

8. Nathan Knowler 42 min later

   @zachleat "use client" coming to 11ty.

9. Andrew Douglass 53 min later

   @zachleat

   1. Zach Leatherman 2 days later

      @ardouglass this is karen behavior andrew!!

10. Darby M. Dixon III 1 hr later

    @zachleat

11. Mike Mathew 2 hr later

    @zachleat 🤣

    1. Zach Leatherman 2 days later

       @drumsensei it’s only a mistake if you use it wrong… wait

12. Private reply 2 hr later
13. Tim Severien 9 hr later

    @zachleat Finally, 11ty SPAs!

    1. Zach Leatherman 2 days later

       @timsev these are fighting words

14. Pascal 10 hr later

    @zachleat First time a screenshot has this huge impact on my plans ! Thanks !

    1. Zach Leatherman 2 days later

       @eQRoeil well now you have to reveal your plans

       1. Pascal 2 days later

          @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.

          1. Pascal 2 days later

             @zachleat I also think it will be easier to make previews and offer alternatives to git based CMS / workflows.

             1. Zach Leatherman 2 days later

                @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!

                1. Pascal 2 days later

                   @zachleat not building clientside for end user (I'd take the lambda / serverless functions route or use Nuxt)

                   Only on the "edit app" part

15. Erik Kroes ✅ 14 hr later

    @zachleat slowly put down the keyboard...

    1. Zach Leatherman 2 days later

       @erikKroes ahahahahahahahaha web performance zach is dead

       long live SPA zach

       1. Patrick Haug 2 days later

          @zachleat oh my oh my

          1. Zach Leatherman 2 days later

             @derhaug (this is a joke of course, not doing the SPA thing here)

             1. Erik Kroes ✅ 4 days later

                @zachleat @derhaug (or are you?)

                1. Patrick Haug 4 days later

                   @erikKroes @zachleat So many ideas already ..

16. Tyler Sticka 16 hr later

    @zachleat

17. Manuel Matuzović 2 days later

    @zachleat ☠️

    1. Zach Leatherman 2 days later

       @matuzo ⚰️

       1. Dave 🧱 2 days later

          @zachleat @matuzo 🪦

          1. Khalid ⚡ 2 days later

             @DavidDarnes @zachleat @matuzo 👻

          2. Eric Portis 2 days later

             @DavidDarnes @zachleat @matuzo 👻!

18. Private reply 2 days later
19. d3v1an7 3 days later

    @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?

    1. Zach Leatherman 3 days later

       @d3v1an7 what runtimes specifically? I’m aiming for all core plugins to be supported yeah

       1. d3v1an7 3 days later

          @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.

20. Zach Leatherman 5 days later

    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.

    1. Alesandro Ortiz 🇵🇷🏳️‍🌈 5 days later

       @zachleat sorcery (good)

    2. Jason Garber 5 days later

       @zachleat •extremely doctor ian malcolm voice•

       your scientists were so preoccupied—

    3. Zach Leatherman 6 days later

       (for the record, the use cases here are limited — and should be limited — please JavaScript responsibly)

       1. Andrew Douglass 6 days later

          @zachleat I’d like to see @cory use this to generate his PHP and run said PHP with php-wasm.

          1. Cory Dransfeldt 6 days later

             @ardouglass @zachleat I’m waiting for PHP to be added as a supported templating language.

    4. mb21 6 days later

       @zachleat I’ve been tinkering with something similar (running a SSG in the browser), what’s your goal here?

       1. Zach Leatherman 6 days later

          @mb21 I probably won’t reveal the ultimate goal (yet!)

21. Raymond Camden 6 days later

    @zachleat so freaking awesome