I was going through the 11ty docs and noticed that 4.0 is right around the corner. The most notable change with 4.0 11ty will also have a client side version of 11ty that could be used.
As mentioned in this thread:
It can likely be used for previews within a CMS.
Here are two examples of it being used in the wild on 11ty’s documentation
I’d be interested in hearing from the community if there are any use cases where or situations that weren’t possible that now are with client side 11ty.
This is actually the first time I’m seeing these new changes coming in 11ty 4.0 It looks promising that this will make the internals of 11ty live rendering much more straightforward for us to maintain at least!
While not directly related to this release, we have been working on some big changes to how live editing works generally that we’re very excited about! We’re not quite ready to share any details yet but we’re hoping they’ll address some of the most common pain points with visual editing and the new client side 11ty may very well play a part in that.
And of course any 11ty updates will continue to make their way into Bookshop once they’re ready for the general public!
Hi Tate! On the subject of keeping Bookshop up-to-date with Eleventy, could I ask the team to look at this issue that I reported in March that never got a response? The Eleventy ecosystem is fast becoming ESM-only, which is making it more and more difficult for me to keep using a CJS config file, which Bookshop seems to require.
4.0 is right around the corner. The most notable change with 4.0 11ty will also have a client side version of 11ty that could be used.
team to see if this will change how 11ty live rendering works within the CMS. 
It looks promising that this will make the internals of 11ty live rendering much more straightforward for us to maintain at least!