There are certain times when you don’t need to give photo credit, such as when you purchase a stock photo. By not giving proper credit, you’re actually breaking the law and opening yourself up to a potential lawsuit. The creator deserves to have others know where their work came from.įinally, your work is automatically copyrighted the moment it’s created. Just as you spent time crafting blog posts and content for your website, so did the person who created the images you’re using. Plus, it’s common courtesy to give credit to the creator. Also, outbound links to high-quality sources can actually benefit your SEO, potentially giving your website a boost in Google rankings. Although there’s a slight chance that could happen, you are actually building trust with your audience by showing them that you give credit where credit is due. You may be concerned that by linking elsewhere, you’re sending website visitors away from your website. But before you upload a photo and call it a day, you should understand how to properly credit a photo - and why it’s so important. Here is everything what you need, if you’d like to use that plugin also on your website as well (or follow the instructions from the GitHub repository).When using visual content on your website or social media, you may need to source others’ images. This plugin, written in ruby, automatically downloads all links of entire flickr photosets and embeds them on the desired Jekyll page via a Liquid tag. I found it: the jekyll-flickr-photoset ꜛ plugin by Jérémy Benoist ꜛ ( see it in action). I therefore searched for any existing Jekyll plugin or script that would do the job for me automatically. A good idea at first glance – but setting the relinks manually for each and every image would have been extremely tedious. So I thought, I just relink the images on my website to the image versions on flickr, and delete the versions on GitHub. In parallel to my website, I usually post my images on flickr ꜛ. I was therefore forced to find another solution, and I found one. Since then, GitHub Actions stopped building and deploying the website and I couldn’t update it anymore.
This worked fine until I reached a certain amount of images and total files size.
In the past, I stored all images of my Weekend Stories in the website’s repository. However, in case you are a photography enthusiast and you’d like to use your website to showcase your photographs, you might reach a limitation by GitHub if you have a huge amount of images. Of course you can keep the images that you embed on your Jekyll website in your website’s GitHub repository. Embedding flickr photos on your Jekyll website
0 kommentar(er)
