All Windows SKUs fall into four different market segments: Server, Business, Consumer and Embedded. Enterprise (which is a "Business" edition) is the "base" version of Windows: in the Microsoft build labs, they compile Enterprise (this is why Insider versions, build leaks etc. are all Enterprise), then add/remove parts, and/or change some settings, to target different markets. Then they throw in a license agreement suitable to that market segment, and off they go.
This is how the market segments are divvied up:
>add server components = server editions
>do nothing = business editions
>hardwire certain config options, remove high-level parts = consumer editions
>remove low-level parts = embedded editions
The segments are then further divvied up to make the actual SKUs. Server editions:
>do nothing = server datacentre
>remove highend server components = server standard
Business editions:
>do nothing = enterprise
>change a couple of registry values to be "kid friendly" = education
As an aside, while Education is technically a "Business" edition (and as such, based on Enterprise), it's often included in "Consumer" edition Windows ISOs for some reason.
Consumer editions:
>do nothing = pro
>re-enable workstation features = pro for workstations
>change a couple of registry values to "kid friendly" = pro education
This is the difference between the Education and Pro Education SKUs: the former is an Enterprise-derived "Business" edition, the latter is a PfW-derived "Consumer" edition.
>remove all support for active directory = home
Microsoft include a lot of management tools (such as the User Manager, Group Policy Editor etc.) in the "Active Directory support" section of the Windows source code: removing AD support removes those tools too. This why Home is such an unconfigurable SKU.
Embedded editions:
>remove all user-facing uwp apps and slap on extended support = [iot] ltsc
>remove the ui, add server components = server core
>remove as much as you possibly can = windows pe