There is a friction point here, but like 8Dweb alluded to, its naysayers complaining. Instead they'll miss out on a good thing because they wasn't openminded enough to investigate themselves. As the saying goes: you can lead a horse to water but you can't make it drink.
I've gotten used to it, but it was little jaring to start with. After seeing the dynamism of the sites and how modular everything is. I am at a loss to think of a better more accurate term. Container is probably the closest, but not so end-user friendly. Packages are like accounts, and Customers are like users. Website(s) are quite fluid in where they could live in an estate. Being part of at least A container somewhere, and the first container being the root domain (website)
I honestly see this as an artifact of enhances success on truly modularising everything and making it so fluid.
Customers>Packages>Websites(s)
Customers>Packages>Container>Website(s)
Or is it Packages are in fact themselves containers? I thought the root website was the primary container of website(s)/domains, giving you the opportunity to put other domains/websites within that space. Or separate it for more security.
There more we can discuss it as a community the easier it would be to find a way to explain it to others. Not necessarily changing the nomenclature, just a more articulated way that's better received.
