vcpkg portfile functions incoherence, specifically "make"-related

[gemelen]

I'm mostly working in a private registry to package some libraries that we need for a project, using vcpkg as a driver and as an example.
Through this journey I saw a lot of missing steps on how to do so, here and there. Most of the times it's possible to find out by reading a port source or a portfile function's CMake source, but this quite a tedious work on its own.
Recently, I was working on a custom sqlite package, which requires switching from CMake to make.
This process reveals that portfile functions for make exist in two flavours, provides slightly different functionality and which are incompatible with each other:

• vcpkg_configure_make, vcpkg_build_make and vcpkg_install_make
• vcpkg_make_configure, vcpkg_make_configure
  And only in the vcpkg_make_configure page there is a mention that it's a replacement for the vcpkg_configure_make].

It's not just a documentation issue per se, but a bit of a whole incoherence between portfile functions and thus, a vcpkg functionality, for those who port libraries into vcpkg approach.

I'd like to initiate a discussion in order to arrange/update/sync all existing portfile functions and to create some kind of a policy on how to keep them in sync with each other, providing both a stable, maintainable framework for the port development, and an opportunity to evolve vcpkg itself.