🐞[Bug]: Multiple Projects Fail to Load Assets Correctly After Deployment Due to Inconsistent Relative Paths

[mrdeyroy]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

[BUG] Multiple Projects Fail to Load Assets Correctly After Deployment Due to Inconsistent Relative Paths

Description

Several projects inside the repository work correctly in local development environments but partially break after deployment because of inconsistent or incorrect static asset paths.

The issue mainly affects:

• CSS files
• JavaScript imports
• Images/SVGs
• Fonts
• Background assets

Many projects currently use mixed path styles such as:

• /assets/...
• ./assets/...
• ../images/...

These paths behave differently depending on the deployment platform and project folder depth, causing assets to fail loading on platforms like GitHub Pages and Vercel.

---

Current Behavior

Some deployed projects show:

• Missing styling
• Broken images/icons
• JavaScript functionality not working
• Missing fonts
• Empty sections caused by failed asset imports

In some cases, projects work locally but fail only after deployment.

---

Steps to Reproduce

1. Clone the repository
2. Open projects located inside nested directories
3. Deploy any affected project using GitHub Pages or Vercel
4. Observe broken CSS/images/scripts in the deployed version

---

Possible Cause

The repository contains multiple standalone projects created with different folder structures and asset import conventions. Some projects rely on absolute paths that are not deployment-safe.

---

Additional Notes

This issue appears to affect multiple older projects and could improve overall deployment reliability across the repository.

I would like to work on this issue and submit a PR for it. Kindly assign it to me if approved.

Expected behavior

Expected Behavior

All projects should load assets consistently in both:

• Local development environments
• Production deployments (GitHub Pages/Vercel/etc.)

---

Proposed Solution

• Audit asset references across projects
• Standardize relative path usage
• Replace deployment-breaking absolute paths
• Ensure compatibility with nested folder deployments
• Validate all assets after deployment testing

---

Add ScreenShots

No response

What browsers are you seeing the problem on?

Chrome

Record

• I have read the Contributing Guidelines
• I want to work on this issue
• I am a part of gssoc26

[github-actions]

Thanks for opening this issue! 🎉 We'll look into it as soon as possible, estimated time for response is 5–8 hrs.

Don't raise PR unless assigned to you.

In the meantime, please provide all necessary details and context to your issue — screenshots or videos of your changes help speed up the review and assignment. If you have questions, reach out to LinkedIn. Your contributions are highly appreciated!😊

Note: I maintain the repo issue every day twice at 8:00 AM IST and 9:00 PM IST. If your issue goes stale for more than one day, you can tag and comment on this same issue by tagging @sanjay-kv.

We are here to help you on this journey of open source. Consistent contributions are eligible for sponsorship 💰

🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨

📚Resources which can help you know more about Github 👇🏻

1. End to End GitHub Beginner Playlist: GitHub Playlist.

2. Build your GitHub Profile: GitHub Profile Optimisation.

3. GitHub Handbook for dummies: GitHub Blog for Beginners.

[github-actions]

Thanks for opening this issue. To help maintainers review it faster, please add the missing details below:

• Steps to reproduce across multiple different projects may need more detail on which specific projects are affected.
• Information on what folder structures are being used in different projects would be helpful for context.
• Details on how the asset paths are set up in a specific project would clarify the issue further.
• Any specific examples of the asset paths that lead to issues would be beneficial.

[github-actions]

✅ This issue has been closed. Thank you for your contribution!

[aaniya22]

please assign this to me under gssoc'26

[mrdeyroy]

please assign this to me under gssoc'26

This is not a valid issue that's why i closed it!
check other issues.