How do they connect? Abp, AbpZero, AbpZeroTemplate[MyCompany] : It's so confusing and unclear how the repositories are connected and tied together. Each git repo has a different package of cs files, with their own unique features and design schemas. Rather than a hierarchical design structure, where in my understanding or example:

**Abp**-base (free git repo), would have core essentials

**AbpZero**-paid (membership subscription to premium git repo), would add additional features into their design that would encourage others to pay for

**AbpZeroTemplate**-demo (download from website, not git), would be a sample utilizing the paid content to push and drive sales to unlock the tool to it's full potential.

I downloaded and even paid for the different tiers, but all of the contents are all over the place. When i tried to combine them so that i could take advantage of a complete product. Nothing lined up properly, and i get breakage everywhere.

How am i supposed to change the crucial schema design flaws when half of the `.proj` links to `.dll` that expect the class to be structured a certain way?

>__Example:__
>`User` is structured: "Name", "Surname". But i want it to be "Firstname", "Lastname." Some may ask, what's the difference? Just like how "Maiden name" is different from "Last name" or "Family name." Those little nuances arent procedual thinking. If you went to a stranger and asked *"what's your name?"* and they said "Chuck Jones," you would then ask to clarify, *"What's your first name?"* 

Each git repository is running off of a different versioning number, that doesn't match with their counterpart. AbpZero is on a stable release version 5.x, and you go to github for Abp and it's saying version 3.x is stable and green. And then to add the cherry on top, one of them is using `User<TTenant,TUser>` as a class, and the other is using `User<TUser>`. So not only am i getting mixed signals on how they're supposed to work (because git repo's point to each other, and rely on .dll for continuity) but they're also not even sharing the same coding structure.

I wish i had enough money as the next guy to afford throwing around $1600 a year just to resolve issues with poorly documented code, but sadly i do not. Can anybody help me merge the old and new together, or tell me the direction on how the design is being built? My membership expired while i was resolving conflict issues with the code, and i immediately lost the ability to use git repo connected to that service. Which is a little frustrating cause i wasnt able to fork branches tied to that premium github and only had the option of downloading code, and rewriting files that were modified by drag and drop methods...