Embedded Images

Hey AbelardoLG,

Don't you have assets/ directory in the root of your project? I suppose you didn't download the code and work in your own project, right? In this screencast we set path to the source images, but you set it to the built images, i.e. Encore build directory "public/build/". I think you need to point to dir where your source images are located. I mean, the images come to public/build/assets/images/ somewhere from another "source" directory that you should link to instead. Because Encore build dir should be in .gitignore

Cheers!

Hi there,

I am build this app on my pace.

My assets directory is included into public dir which is under the root.

I am going to investigate why it happens. :) Brs.

Hey Abelardo,

Yeah, just point it to your assets directory in public/ folder, but not to the public/build/ directory yet. :) We will point to build directory later, but for now we want to point to the image source directory.

Cheers!

Hi Victor, posting this message here as you raised this point. I have to admit that I have just done a few chapters here and there to learn a few specific things about Mailer - I might have missed out where this is done. However, checking the code in the /finish directory, should the twig.yaml file not have the path to the build directory? Or did I miss out something?

twig:
  paths:
    'public/build/images': images

Hey Martin,

It depends on what you need. If you only want to have an ability to load only images from the Twig templates - you will be enough to point only to your image folder in the public/ dir. Actually, it depends on if you handle all your images via Webpack Encore or no. If you do - then yeah, you would need to point to the build/ directory, but once again you may want to point to a specific image directory in that build/ folder. In this course project we just didn't handle images that we're using in emails via Webpack Encore, that's why our images are in "assets/images" and not in "build/", that's it, but it may be different for your custom project, depends on how you do things in it.

I hope this helps!

Cheers!

Hey Evelyn P.

If the API is returning the image file paths, then, it should return them as absolute URLs. But, if you're talking about the images loaded by your frontend app (let's say, in order to load its own design) then having a base path stored somewhere makes sense (in a Twig file, or in the frontend app itself)

Cheers!

Hey Tomasz,

Thank you for your feedback! Agree, it's not that useful at all, though probably makes sense to change it to "SymfonyCasts Logo"? Or just "SymfonyCasts"? Or are you about to do not use alt text at all? Because, IMO using some alt text would be good for SEO.

Cheers!

The truth is that img[alt] is not meant for SEO. It's meant for a11y technologies like screen readers and for text browsers (like for people who are in process of installing Arch Linux :) ). If your image is decorative (like borders, separators) it should container empty alt="". Don't skip alt at all — in that case screen reader can read filename. If your image contains logo or some banner with text, alt should container exactly that text. For example Foo company logo with "Foo" word and some icons should have just alt="Foo" attribute. The most complex case is with photos and charts — here you have to describe the whole image. Sometimes it might be good idea to just link to another page with text representation, instead.

Thanks again for the advice on this TomaszGasior :)