Images and files

Landing pages. Pictures go to images/ and are referenced by file name from the content (image="hero.jpg", image="logos/acme.svg"). The build generates responsive variants in webp and marks the pictures that decide the loading score as high priority. Files that must be served untouched — PDFs, archives, anything downloadable — go to assets/ and are linked as /assets/<file>.

Knowledge bases. Put images next to the page that uses them and link them relatively; put downloadable files under assets/ and link them relatively too (assets/manual.pdf, ../assets/manual.pdf). Both render in GitLab and on the site.

Original files never reach the site for images that were optimized; assets are copied as they are.