Edited as per Teo, makes it a bit less confusing.
I have worked quite a bit with Layout -> Content -> Partials and yes it can be a bit of a pain.
From my experience its a bit of a manual task to be honest, as I manually make sure in my Layout Page which holds the <head></head> section that I add all components that are common, such as browser, notify, alert, toasts, as all those are just dummy containers that I will dynamically populate with dynamic data, as well as styling, and the browser component, well I normally only have one at the base of the site which I reuse.
Then I may have a few Content pages, honestly not too many, maybe 4 at most, and in those I am storing vastly different layouts, like one is a blog layout, one is a product page layout, etc.
In these if its a fairly small site you can just stick everything and not really worry about partials.
Personally I am a partial fan, so my content pages are generally just full of links to different partial files, each partial contains its own <serverconnct></serverconnect> that are relevant to the content of the partial.
It can at this point be fairly difficult to access the bindings in the pickers as you will not see most of them from the partial file, so I kind of switch between tabs manually getting whats needed, often creating the element first inside the content page, and then moving it to a partial at the end of that section.
Hope this helps a little.
