Given I have no experience in Ruby and thus Rails and its development environment, this will be quite the learning experience (I have a [C++/Java]/C/Shell/Perl background), and not something I can commit to at the moment; as I wish to get my Foreman server and remote Smart-Proxy up and going, to work on actually provisioning some systems :-). But if time permits I’ll look into it.
I’m currently merging the notes, I have taken on building Foreman 2.1.0rc* (on CentOS 7 & 8) on the command line into a single readable document, and extending it to cover setting up provisioning (principally via the CLI). So I can reproduce my Foreman systems, if/when required (especially given "foreman-maintain backup" fails on CentOS8 / Foreman 2.1.0rc* - Multiple Issues) and determine if and how to automate its construction further down the line. My initial provisioning testing was done via the WebUI on 2.1.0rc1, and I have learnt a lot since that work.
Once I have a Foreman 2.1.0 (non-rc*) system up and successfully provisioning systems, I would like to post that write-up to the community, as way to document my adventure (and receive feedback on it correctness), for those who may embark on such a journey in the future. [ “Pass on what you have learned.” – Yoda ]
Which given my current very positive view of the Foreman, I hope others will discover Foreman, and get their first Proof-of-Concept going and more importantly, their understanding of the Foreman ecosystem embedded a little more quickly than I did (maybe I’m getting old 
). But at least now, I can say I have read most (but probably not all) of the product documentation 
. You may have noticed from my posts, that I have actually been trying to treat Foreman as product (or blackbox), and not dive deeply under the covers - but as a programmer there is always the desire to dive in - I have been trying to suppress that. [ But: "Impossible to see the future is.” – Yoda ]