Leider kann ich ja nicht Eure Kommunikation im “Private Content” nachvollziehen ( als Participant ) aber wenn ich mir die Demo auf einem iPad ( real device 10.5 ) anschaue, dann sehe ich da keine Aussetzer. Lediglich das Umschalten von fixed auf scroll ist üblich, da wohl Safari schlecht mit background-attachment: fixed umgehen kann.

Welchen Grund hat es, das Ihr “mobile” Sektionen erstellt? Stimmen dann die Bildausschnitte nicht mehr? …

_____________

Unfortunately I can’t follow your communication in ‘Private Content’ (as a participant), but looking at the demo on an iPad (real device 10.5) I don’t see any dropouts. Only switching from fixed to scrolling is common, as Safari is probably bad at background attachment: fixed.

Why do you create ‘mobile’ sections? Are the image sections no longer correct? …

Oswald ist einer dieser Fonts die bereits bei Google als variabler Font angeboten werden. Variable Fonts können auch Zwischenwerte annehmen. Häufig betrifft dies nur das font-weight, aber auch andere Werte wie font-höhen font-breiten etc.

Bei Oswald ist es in der Tat nur das font-weight. ( Einer dieser “Super Fonts” ist z.B. Roboto Variable ).
Wenn du also Oswald bei Google downloadest, dann erhältst du den variablen Font und in einem gesonderten Ordner (static) auch die statischen (traditionellen) Font Varianten.
Dieses zip welches du bei Google heruntergeladen hast, ist so nicht geeignet in den Font Manager von Enfold hochzuladen.

Jetzt gilt es eine Entscheidung zu treffen. Nutzt man wirklich die Möglichkeit eine Schriftdefinition von font-weight: 334? ( das müßte man auch im css so anlegen ) braucht man alle font-weight von 200 bis 700 bei Oswald? Oder ist man zufrieden, die gängigen Werte zu akzeptieren und beschränkt sich auf 300, 400, 700.

Moderne Browser ( und das sind mittlerweile fast alle ) unterstützen zudem das Format woff2, welches aus performance technischen Gründen die bessere Wahl ist. Google bietet jedoch nur ttf an. Statische Schriften vermögen etliche online Tools gut in woff2 zu wandeln. Bei den variablen Fonts versagen oft alle online Tools. Ich nutze ein Command-Line Programm um solche variablen Fonts in woff2 zu wandeln. – ist aber nicht jedermanns Sache.
gute Beschreibung : Link

Wenn man nun alle ttf ( würde ich als Fall-Back Lösung mit hochladen für die älteren Browser ) und woff2 hat, die man möchte:

die Statischen Fonts (ttf und woff2) in einen Ordner legen – den variablen Font in einen weiteren Ordner (ttf und woff2) – den einen nennst du Oswald – den anderen z.B. Oswald Variable.
Diese jetzt packen ( am PC gibt es keine Probleme; bei Mac zum Packen ein Programm wählen, wo man die mac spezifischen meta Daten ausschließen kann (BetterZip …)) . Diese zip sind nun bereit für den Upload in den Font Manager von Enfold.

Meine Empfehlung : nimm nur das zip mit der Auswahl von statischen Fonts. Bei der Nutzung der variablen Fonts muss man beim Einrichten der Fontnutzung noch an User denken, die ältere Browser in Benutzung haben, welche keine variablen Fonts umsetzen können.
https://caniuse.com/variable-fonts

Wenn Sie jedoch der Meinung sind, dass die wenigen Personen, die ältere Browser verwenden, zahlenmäßig und von der Bedeutung her vernachlässigbar sind, dann reicht es aus, die variable Schriftart zu verwenden und sogar nur die woff2 im Zip zu belassen.

Hier mal die zip für Oswald – entscheide selbst:

Oswald: Link1
Oswald Variable: Link2

__________________
translation by deepL:

Oswald is one of the fonts that Google already offers as a variable font. Variable fonts can also take on intermediate values. Often this is just the font weight, but other values such as font height, font width, etc. are also possible.

In Oswald’s case, it is only the weight. (One of these “super fonts” is, for example, Roboto Variable).
So if you download Oswald from Google, you will get the variable font and the static (traditional) font variants in a separate folder (static).
The zip you downloaded from Google is not suitable for uploading to the Enfold Font Manager.

Now you have to decide. Do you really need to use a font definition with weight: 334 (you would also have to create this in the css), do you need all the weights from 200 to 700 in Oswald? Or are you content to accept the default values and limit yourself to 300, 400, 700?

Modern browsers (which are now almost all) also support the woff2 format, which is the better choice for technical performance reasons. However, Google only offers ttf. A number of online tools can convert static fonts to woff2. For variable fonts, all online tools often fail. I use a command line tool to convert such variable fonts to woff2. – But it’s not for everyone.
Good description: Link
Now that you have all the ttf (I would upload this as a fallback solution for the older browsers) and woff2 fonts you want:

On the other hand, if you believe that the few people who use older browsers are negligible in number and importance, then it is sufficient to use the variable font and even leave only the woff2 in the zip.

Put the static fonts (ttf and woff2) in one folder – the variable fonts in another folder (ttf and woff2) – one you call Oswald – the other e.g. Oswald Variable. Now zip them (no problem on a PC; on a Mac, choose a zip program that allows you to exclude the Mac-specific metadata files (BetterZip …)). These zip files are now ready to be uploaded to Enfold’s Font Manager.

My recommendation: only use a selection of static fonts. When setting up the use of variable fonts, users who use older browsers that are unable to handle variable fonts must be taken into account.

Links of Oswald Font see above.

thats why i wrote:

Mostly there is the opportunity to edit the child-theme functions.php via Dashboard: …

some Providers or Security Tools hamper that Option.

do you use a child-theme ?

see here the documentation: https://kriesi.at/documentation/enfold/child-theme/

This is my recommended use of WordPress themes. You can easily change the settings of the parent theme – and these will be retained even after updates.

A child theme has on start ( you see the link above got a preset child-theme to download ) these three files : style.css / functions.php and a screenshot.png
in style.css there is the info of parent theme name and how to find the template
the functions.php is at start nearly empty ( editing that file : do not overwrite the first line )
the png is only to have a preview on themes overview.

A child theme is placed besides the parent theme

Yes – that discussion is now from me to the devs or mods – and my hope is that it will find a solution then for you.
______________
we can have that filter :

function change_max_columns_on_mega_div($args){
  $args['max_columns'] = 7;
  return $args;
}
add_filter('wp_nav_menu_args', 'change_max_columns_on_mega_div', 10, 1);

but we had to find now a solution for the missing calculation of positioning the mega-div for that case

first : do not set on menu – that there should be a new row:

We do this by our css !

my solution would be to use grid layout on that :
7 1/4 columns with no equal height inside a color-section with a custum-class

see: https://webers-testseite.de/apg/

My recommendation for images that should look the same: Crop them the same way – that is, keep them at least in the same aspect ratio.

on image elements – this selector avia-image-container-inner is best for it but if you try to have it on columns – the selector might be better the flex_column itself:

.flex_column.polygonright {
  -webkit-clip-path: polygon(0% 0%,68% 0%,100% 50%,68% 100%,0% 100%);
  clip-path: polygon(0% 0%,68% 0%,100% 50%,68% 100%,0% 100%);
}

ps: do not forget to use both clip-path and webkit-clip-path

i can simulate my code on transfering the script to developer console to see if it works

this is already done by the language files (for your language too, I hope), in German this is the case.
see here a blog example page ( the green Titles) : https://webers-testseite.de/masonry-blog/

and a bit of css:

.av-masonry-entry-title .av-masonry-comment-count {
  font-size: 0.8rem;
  color: #666
}

but isn’t it an existing feature inside postslider.php to show the comments count?
Enfold – Blog Layout – Blog Meta Elements

I would recommend using html entities. Unfortunately, even there it is sometimes the case that a new call of the editor mode / visual mode leaves them effective or not, but they are no longer visible in the backend. One example is the so-called softhyphen – a conditional hyphen.

Günter has created a plugin with which it was possible to set the characters larger / smaller as well as in the layout elements, without them being evaluated as tag beginnings. Since I didn’t want to put 3 # characters before and after the abbreviation, I shortened it to one # character and extended the list that could be used with the plugin.

So if i would like to have an invisible Space at the beginning of one line i inserted instead: #nbsp#

See the plugin here: https://pastebin.com/jttc230x
Download it here: specialcharacter Plugin

just put it into your plugins folder via ftp

Die Methode über eigene Sprachfiles ( de_DE_formal.po/de_DE_formal.mo und de_DE.po/de_DE.mo) ist prinzipiell sauberer.
Dazu müsstest du die po files bearbeiten und eine Kopie (vorzugsweise in den Ordner “lang”) im child-theme folder platzieren.
Dem Thema muss man dann noch sagen wo die Files liegen:

function overwrite_language_file_child_theme() {
    $lang = get_stylesheet_directory().'/lang';
    return $lang;
}
add_filter('ava_theme_textdomain_path', 'overwrite_language_file_child_theme');

Bearbeiten kannst du die Files mittels poedit – Du musst dort die englische Phrase finden, und die neue deutsche Übersetzung dann einfügen. ( es kann mehrere Stellen geben wo das auftritt.) Poedit speichert dann beide Versionen (po/mo) ab. Diese in den Lang Ordner hochladen.

Deutsch ist nochmal ein Sonderfall, weil es meherer Sprachfiles auch schon wegen Du/Sie gibt.

___________________

The method using your own language files ( de_DE_formal.po/de_DE_formal.mo and de_DE.po/de_DE.mo) is generally cleaner.
To do this, you would have to edit the po files and place a copy (preferably in the ‘lang’ folder) in the child-theme folder.
You then have to tell the theme where the files are located:

see codesnippet above

You can edit the files using poedit – you must find the English phrase there and then insert the new German translation. (There may be several places where this occurs.) Poedit then saves both versions (po/mo). Upload them to the Lang folder.

German is another special case, because there are already several language files because of different salutations: Du / Sie.

I can’t find the passage either in one of the Enfold files or in the Lang files of the translation for the various languages.
The maximum you can always find is “password protected” – so it seems to be a WordPress setting.

Hooray – there are WordPress filters that do that: try in your child-theme functions.php:

function change_protected_title_prefix() {
    return 'VIP membership required: %s';
}
add_filter('protected_title_format', 'change_protected_title_prefix');

if it is the german version you had to translate it by yourself
if you do not like the double dot – get rid of it

PS: if you like to use quotes inside that phrase you had to use entities f.e.:

function change_protected_title_prefix() {
    return 'VIP’s only: %s';
}
add_filter('protected_title_format', 'change_protected_title_prefix');

_________
by the way: if the post is private – and you do list them

function change_private_title_prefix() {
    return 'Admins only: %s';
}
add_filter('private_title_format', 'change_private_title_prefix');