Hello, being doing some investigatory work on putting 'template items' into uSync. https://github.com/KevinJump/uSync/discussions/525 - Its something that has been there or thereabouts forever, and yes it sounds a lot like 'blueprinting' - but in my defence, I was "blueprinting" Tridion websites, like 18 years ago now - so this isn't a new thing. We even talked about blueprinting in uSync 2.x I think. Real question : having spent two days on it, is .. is this a worthwhile thing ? (and please don't just say yes it looks cool!, think would you actually use it?) any comments / ideas welcome. on the discussion.

(👀 reading now) ... to clarify, do you mean the parent/child are separate Umbraco instances? did you mean a similar concept to Umbraco Cloud's Baselines feature?

Yeah separate instances , you would prob have a site with the basics and somehow get those files into the base folder of another site (deployment of the files isn't uSync's job)

gotcha, sounds ace, (and trying not to say "yes, it looks cool") ... if the feature was available, I'd definitely want to use it on those boilerplate websites (that I keep finding myself get involved in). Old Carlsberg brand websites or more recently the Playmaker (sports websites) from Gibe. It'd make sense for rolling out underlying updates (to content/schema), whilst letting the derived (child) website have its own customisations.

This seems really useful to potentially set up for rolling out a new feature that's a big website section and not having to force the client (or one of us) to create the underlying structure of all their new pages on their authoring site. They'd still have to fill in content, but getting them through that hurdle definitely seems like a nice quality of life option!

Yes, this would be awesome, and I might even know of a project that would benefit from it