We hardly ever use complete website interface, and build our interfaces from scratch or some sort of general-use design/config base. Some of the reasons:
- website interface is indeed an interface - includes lots of logic and dedicated solutions, which do not match our needs or preferences in most cases (that includes fetches, caching layer, organization of templates).
- website interface is complex enough (as you noticed) to take some time to learn, which make sense only if you're keen to learn or find ezwebin useful for your purposes.
- website interface's design, because it is highly repeatable, is not acceptable for our customers. - website interface's partial adaptation for a project makes future development of the project more expensive than with dedicated interface.
However, website interface is a good place to look for patterns, examples, generally learning for implementing your customized solutions, a good source of practices and conventions to follow.
