No. You can add a field to the site page, and access it anywhere. You do not need to add the image to every page, just the site options page that you can get to by clicking the button in the top left of kerbis panel, and choosing site options from the dropdown.
This is where i put any logos or any imagery used in the footer. Basically you have an image field added to the site.yml blueprint then you can get it though $site. I just happened to call my field sitelogo().
So my site blueprint contains this:
label: Site Branding
label: Site Logo
label: Site Alternative Logo
Then in a template or snippet you can retrieve it with <?= $site->sitelogo()->toFile()->url() ?> and this will work on any page. It is a good idea to check the field has a value like i did above, other wise you will get an error if its missing:
Then where do we instruct the program to pick up the logo file? The php above states that its a thing and then it tells the code to look for said thing but im not sure were we are telling it where to find the logo and where to place the files itself (im assuming in the images folder per usual). correct me if im wrong on any of this please!
For what i call a global image, like a site logo, or social media images used in a footer, I add these to the site page (that you can get to by clicking the button in the top left of kerbies panel, and choosing site options from the dropdown). I like to use fields, because its an easy way to let clients change them without dictating the filename to them becuase it will break if that changes. If you don’t want a field and wish to use the image directly you can do it like this, you can add it to the site options page and then do this in a template or snippet:
@opelandia It might be worth you working through the tutorials in the cookbook. Will probably clear up a few concepts. Try the blog tutorial and the onepager. Also, theres a good guide on all things images.
I usually put the logo and all other files that should not be changed/selected or even accidentally be deleted by the user (like icons used on the site) into the assets/images folder. Files that the user is supposed to upload or select either go into the site folder (i.e. directly in content) or into the individual page folders.