Skip to content

Relocate /assets/images/partner to static/partners#7268

Open
asgharali97 wants to merge 6 commits intolayer5io:masterfrom
asgharali97:chore/relocate-partner-logos
Open

Relocate /assets/images/partner to static/partners#7268
asgharali97 wants to merge 6 commits intolayer5io:masterfrom
asgharali97:chore/relocate-partner-logos

Conversation

@asgharali97
Copy link
Copy Markdown
Contributor

Description

This PR fixes #7256 by relocating assets/images/partners to static/partners and updating all references to use absolute static paths.

Dynamic image imports were replaced with string-based "/partners/..." paths to align with Gatsby’s static asset handling.
This PR fixes #7256

Notes for Reviewers

  • No functional changes beyond asset relocation and reference updates.
  • No imports from static/ are used; assets are referenced via absolute paths.

Signed commits

  • Yes, I signed my commits.

@github-actions github-actions Bot added area/blog New posts or new blog functionality area/events labels Dec 19, 2025
@asgharali97 asgharali97 force-pushed the chore/relocate-partner-logos branch 2 times, most recently from 97975de to 01661a8 Compare December 20, 2025 13:28
@saurabhraghuvanshii
Copy link
Copy Markdown
Member

@asgharali97 build faling please fix that

@asgharali97
Copy link
Copy Markdown
Contributor Author

Hi @saurabhraghuvanshii,
Thanks for telling build failure

I’ve reviewed the CI logs and the error appears to originate from src/templates/program-multiple.js where a non-null graphQL variable ($program) is receiving a null value during page generation (/programs/null.html)

This seems related to existing MDX content under src/collections/programs/ (e.g. hacktoberfest-2023) rather than the partner logo relocation in this PR. I didn’t modify any program templates, collections, or GraphQL logic here.

Please let me know if you’d like me to help investigate or address this separately.

@kishore08-07
Copy link
Copy Markdown
Contributor

@asgharali97
Thank you for your contribution!
Let's discuss this during the website call today at 6:30 PM IST | 8 AM CT
Add it as an agenda item to the meeting minutes, if you would :)

@asgharali97
Copy link
Copy Markdown
Contributor Author

Hi @kishore08-07, Thank you for inviting. I would love to join

@CodexRaunak
Copy link
Copy Markdown
Contributor

@asgharali97 merge conflicts to address.

@saurabhraghuvanshii
Copy link
Copy Markdown
Member

@asgharali97 can you resolve merge conflicts?

@asgharali97
Copy link
Copy Markdown
Contributor Author

Hi @saurabhraghuvanshii ,I noticed there’s another PR (#7439) addressing the same issue and it seems to have passing checks.

Should I still proceed with updating this PR and resolving conflicts, or has that PR effectively replaced this one?

@saurabhraghuvanshii
Copy link
Copy Markdown
Member

@asgharali97 yeah also address the suggestion move images to static/images/patners

@saurabhraghuvanshii
Copy link
Copy Markdown
Member

@asgharali97 are you going to update this?

@asgharali97
Copy link
Copy Markdown
Contributor Author

Hi @saurabhraghuvanshii, Yes, I’m working on updating it. I’ve reset to the latest upstream and am reapplying the changes to align with the current structure. I’ll push an update shortly.

@asgharali97 asgharali97 force-pushed the chore/relocate-partner-logos branch from 6577e4a to 1878ab6 Compare April 27, 2026 19:43
asgharali97 and others added 3 commits April 28, 2026 01:48
Co-authored-by: Copilot <copilot@github.com>
Signed-off-by: Asghar Ali <asgharalifs48@gmail.com>
Signed-off-by: Asghar Ali <asgharalifs48@gmail.com>
Signed-off-by: Asghar Ali <asgharalifs48@gmail.com>
@asgharali97 asgharali97 force-pushed the chore/relocate-partner-logos branch from c718230 to 6f2f9f9 Compare April 27, 2026 20:49
Signed-off-by: Asghar Ali <asgharalifs48@gmail.com>
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 27, 2026

🚀 Preview deployment: https://layer5.io/pr-preview/pr-7268/

Note: Preview may take a moment (GitHub Pages deployment in progress). Please wait and refresh. Track deployment here

@asgharali97
Copy link
Copy Markdown
Contributor Author

Hi @saurabhraghuvanshii, I’ve addressed the issues and updated the PR. It is now ready for review.

Please let me know if any further changes are needed. Thanks!

id={partner.name}
loading="lazy"
src={imageSrc}
src={partner.imageSrc}
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please Update this to partner.imageLink

author: Lee Calcote
thumbnail: "../../../../assets/images/partners/intel-grey.webp"
darkthumbnail: "../../../../assets/images/partners/intel_white.webp"

Copy link
Copy Markdown

@thechillbasu thechillbasu May 4, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why add an extra line? There are several extra lines added throughout the files. I am not sure if its required.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@thechillbasu Thanks for pointing that out! I’ve cleaned up the unnecessary extra lines and kept the changes minimal. Please take another look.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Actually it wasn't that big of an issue but still, sometimes keeping the code structure more uniform is better. And avoiding unnecessary formatting helps the reviewer focus on the actual necessary changes. Most of the formatting was ok, some were actually good but a few were unnecessary but I guess those were unintentional. Anyways, good work. Thanks for your contribution!

id={partner.name}
loading="lazy"
src={imageSrc}
src={partner.imageSrc}
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't this be src={partner.imageLink} since the partners-home-data.js uses the key imageLink?

author: Lee Calcote
thumbnail: "../../../../assets/images/partners/intel-grey.svg"
darkthumbnail: "../../../../assets/images/partners/intel_white.svg"
thumbnail: "/images/partners/intel-grey.svg"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Using an absolute path here might break the blog thumbnail. Because our schema explicitly uses @fileByRelativePath for thumbnails(https://github.com/layer5io/layer5/blob/master/gatsby-node.js#L1213), Gatsby's GraphQL needs this to be a relative path so it can process the image as a File node.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@saurabhraghuvanshii ^^ I’m not sure about this because I can’t build the blog locally either.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rishiraj38 , I think you're correct here.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@asgharali97 please fix here

Image

Comment on lines +47 to +48
imageRoute:
"/company/news/layer5-and-hashicorp-launch-service-mesh-partnership",
Copy link
Copy Markdown

@thechillbasu thechillbasu May 4, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be better to add the path in the same line as the key.

Signed-off-by: Asghar Ali <asgharalifs48@gmail.com>

    fix: correct image source property in LazyPartnerImage component
@asgharali97 asgharali97 force-pushed the chore/relocate-partner-logos branch from 18df128 to a58775f Compare May 4, 2026 16:22
author: Lee Calcote
thumbnail: "../../../../assets/images/partners/intel-grey.svg"
darkthumbnail: "../../../../assets/images/partners/intel_white.svg"
thumbnail: "/images/partners/intel-grey.svg"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@asgharali97 please fix here

Image

author: Lee Calcote
thumbnail: "../../../../assets/images/partners/intel-grey.webp"
darkthumbnail: "../../../../assets/images/partners/intel_white.webp"
thumbnail: "/images/partners/intel-grey.webp"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here Also

thumbnail: "../../../../assets/images/partners/intel-grey.webp"
darkthumbnail: "../../../../assets/images/partners/intel_white.webp"
thumbnail: "/images/partners/intel-grey.webp"
darkthumbnail: "/images/partners/intel_white.webp"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here

thumbnail: "../../../../assets/images/partners/intel-grey.svg"
darkthumbnail: "../../../../assets/images/partners/intel_white.svg"
thumbnail: "/images/partners/intel-grey.svg"
darkthumbnail: "/images/partners/intel_white.svg"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here

Signed-off-by: Asghar Ali <asgharalifs48@gmail.com>
@Sbragul26
Copy link
Copy Markdown
Member

A few things still need fixing — the old /assets/images/partners folder is still there. Since everything has been moved to /static/images/partners , could you please remove the old folder as well?

@thechillbasu
Copy link
Copy Markdown

thechillbasu commented May 5, 2026

A few things still need fixing — the old /assets/images/partners folder is still there. Since everything has been moved to /static/images/partners , could you please remove the old folder as well?

@Sbragul26 I think we can't do that because, as discussed, the blog posts, i.e., the mdx files still point to that folder so that they can be processed through the Gatsby Image Pipeline.

@asgharali97
Copy link
Copy Markdown
Contributor Author

@Sbragul26 Thanks for raising this! Based on the earlier discussion around Gatsby’s image processing, the .mdx files still rely on the assets/images/partners directory for thumbnails via the GraphQL pipeline.

So I’ve kept that folder intact while moving runtime image usage to static/images/partners. Please let me know if you’d prefer a different approach.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/blog New posts or new blog functionality area/events

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Relocate partner logos to appropriate directory in static folder.

7 participants