That actually makes sense.
Ok found out the culprit, the extensions order wasn’t right. SiteConfig gets a CustomSiteConfig extension, and after that you apply the Fluent one. It has to be the last one.
That surely is something that needs to be addressed in the Elemental and/or Fluent documentation, a clear example would help greatly. Hope to make a PR once I get it right.
Ok made all the blocks translatable, apart from the Title field. I wanted to make the custom siteconfig extension translatable before starting to add another language, but can’t seem to summon the right incantation.
Hang on, maybe the CSS decoration isn’t there, but the field is actually translated.
Ok managed to make it work, but cannot translate the block Title, because it gets replaced by a custom field in the BaseElement.
Also tried this