Drupal 8.x

I'm trying to get the field_group module to work with entities that do not use "content" as the property name of the renderable entity content. The module already uses a special case for user profiles. I specifically want it to work with Commerce product variation entities, but a generic solution is the goal. Examples:

$entity->content
$entity->user_profile
$entity->product_variation

Is there a standard method or technique to determine the name of the entity property that contains its renderable content?

I have a project in process; for sake of example, I'll say it is for a Baseball team.

We’re open 24/7 at www.ahml.info.

Consider joining our talented IT team in a role to recommend and develop new web services and applications. You will be responsible for full life cycle development including requirements, coding, testing, implementation and maintenance. Will work with staff and customers to conduct testing and collect feedback to advise our Web Team of possible enhancements for the user experience.

Requirements & Skills:

I have my urls redirected to https in my .htaccess file. Everything works perfectly except the site:url token returns 'http://www.example.com'. So on the 'Basic site settings' page, it shows http for the base url instead of https. And my meta tag urls all have http instead of https. Any ideas on how to change the base url to reflect 'https'? Thanks.

Can I base a new content type on an existing one? Or can I add to an existing content type and then 'save as...'? The alternative would seem to be multiple screen dumps of the existing content type settings and a load of work.

For example the following template code:

<h3>{{ 'Translate this'|t }}</h3>

The source language is set to English so the text 'Translate this' can be translated to another language and edited through the UI by an administrator. However, the original string 'Translate this' can not be changed to i.e. 'Translate me' by the administrator. If it needs to be changed it must first be changed in the template and then translated through the interface (even if the translation still applies).