bvbaked

If you already have a Pages template created, that will apply to all of your pages. If you create another, it will make you choose a single page for it to apply to since you cannot have two. This is because of the file name. Using the example of setting my About page to a custom page template – the default page is saved in a file page.html but now there is a page-about.html that displays my About page.

You can see where this is a bit limited which is where a custom template is useful. A template-two-column.html for example could be made as a custom template and that can be set to multiple pages/posts to use this format

This article on the template hierarchy might help to explain it

If you are using the correct hook then the script will be added server side. That code should always run in the same order so you wouldn’t get the inconsistencies you note. All your scripts should be getting added in the same order and since you don’t have dependencies then it should always be getting included. There is no reason to include jquery as a dependency unless you use it so that would depend on how you wrote it. If this was the problem you might see it in the console with jquery related errors

making sure the initialization runs after the full page load using DOMContentLoaded or window.onload

If you are not having it run on one of the load events, you definitely should. The problem could just be a race condition where your script is running too early and what it needs on page isn’t available. That might explain why you get inconsistent loading as well as it depends on the loading time

 I’d really like to know what you would check first whether it’s enqueue order, plugin conflicts, or script execution timing.

Order matters when scripts rely on something else being loaded. That’s what setting a dependency will do – it puts the scripts on the page in the right order. Conflicts and timing can be more difficult as these can sometimes be more silent. If you’re worried about an optimization plugin (sometimes they can jumble things up) you may be able to exclude it and see if that helps any.

I plugged in a control and refreshed a few times and it always seem to load fine and track my input

Your reasoning is correct and highlights where the featured image becomes important. As part of a template or query the featured image can pull in dynamically based on the page without the need to manually apply the same type of formatting you would need to use an image instead.

Think of it like the page title or excerpt – you could use a heading and paragraph in place of these but it adds a lot of flexibility when used as part of a standard template or format

No problem, looking good!

Is it part of the template?

You wouldn’t see that in the editor but it is possible that if it was included in a specific template that you’d get extra blocks you may or may not want. In addition to checking with the theme support, you may want to look in the editor for this as well

This is not wrong, and not a limitation of the theme or the block editor. It is the expected behavior of flex containers.

If you want it the other way around, you’ll have to use either a flex-direction: column-reverse or set an order. This then introduces some confusion with accessible technology that the content displayed is no longer following the order of what a screen-reader would announce…

I guess if you don’t care about that, then change it, but the way this works is best practice so it doesn’t have to be the other way – that’s just the way you want it

There is little anyone can do without more information. If you follow that link you’ll find some information about debugging

If you enable debugging you should be able to find the source of the error so it can be resolved

For the pagination: you are using grid, so the width of 100% is making it the full width of a cell not the container. You can use this instead:

.navigazione2 { grid-column: 1 / -1; }

For the shadow, I think you’re just seei ng the spread above the element and not three shadows. See if this is a better effect? It will be more like a drop shadow which I think is what you’re after

.archive-header-bar,
.custom-bc-container { box-shadow: lightgray 0px 5px 15px 0px; }

You don’t really see the shadow from the top element though since it is covered by the next div….