there are some missing images from https://github.com/ipfs/blog
when bringing back these image, favor placing them in src/.vuepress/public so they can be found by forestry.io 😉
there are some missing images from https://github.com/ipfs/blog
when bringing back these image, favor placing them in `src/.vuepress/public` so they can be found by forestry.io 😉
examples:
https://ipfsblog-vuepress.netlify.app/_002-ipscend/
https://ipfsblog-vuepress.netlify.app/weekly-008/
<!-- github-sync-id:786706076 -->
I did a little digging and it appears that the original move to put each individual blog post + its images in a separate directory was to accommodate the original Hugo platform.
That said, if we are moving all the images to Vuepress' public directory, we should make sure that someone working in that directory can understand where a particular image is referenced -- right now there are a bunch of images named things like screenshot.jpg and if they are all in the same directory that's super confusing.
If you move all the images into a single directory, can you please prepend the names with the directory they came from (or more accurately, the post they belong to), i.e. weekly-123-screenshot.jpg?
I did a little digging and it appears that the original move to put each individual blog post + its images in a separate directory was to accommodate the original Hugo platform.
That said, if we are moving all the images to Vuepress' `public` directory, we should make sure that someone working in that directory can understand where a particular image is referenced -- right now there are a bunch of images named things like `screenshot.jpg` and if they are all in the same directory that's super confusing.
If you move all the images into a single directory, can you please prepend the names with the directory they came from (or more accurately, the post they belong to), i.e. `weekly-123-screenshot.jpg`?
<!-- github-comment-id:761097552 -->
Yes, that makes sense. I am currently going through the static folder in the old blog and checking if we have all the images in the current one.
When I am done with that, I can move all the media files to the public directory and rename them. Does that sound good?
Yes, that makes sense. I am currently going through the static folder in the old blog and checking if we have all the images in the current one.
When I am done with that, I can move all the media files to the `public` directory and rename them. Does that sound good?
<!-- github-comment-id:761101796 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
there are some missing images from https://github.com/ipfs/blog
when bringing back these image, favor placing them in
src/.vuepress/publicso they can be found by forestry.io 😉examples:
https://ipfsblog-vuepress.netlify.app/_002-ipscend/
https://ipfsblog-vuepress.netlify.app/weekly-008/
I did a little digging and it appears that the original move to put each individual blog post + its images in a separate directory was to accommodate the original Hugo platform.
That said, if we are moving all the images to Vuepress'
publicdirectory, we should make sure that someone working in that directory can understand where a particular image is referenced -- right now there are a bunch of images named things likescreenshot.jpgand if they are all in the same directory that's super confusing.If you move all the images into a single directory, can you please prepend the names with the directory they came from (or more accurately, the post they belong to), i.e.
weekly-123-screenshot.jpg?Yes, that makes sense. I am currently going through the static folder in the old blog and checking if we have all the images in the current one.
When I am done with that, I can move all the media files to the
publicdirectory and rename them. Does that sound good?Sounds good 😊