Skip to content

Conversation

ShubhamOulkar
Copy link
Member

@ShubhamOulkar ShubhamOulkar commented Sep 20, 2025

See discussion #2004

Why this change?

  • Helps us manage assets more gracefully going forward.
  • Makes future redesigns or migrations to a new platform smoother.
  • Improves DX (Developer Experience) and reduces unnecessary clutter at the root level.

Note:- While the diff size is large, a future migration would result in an even bigger diff and introduce more room for mistakes. Handling this restructuring now will minimize those risks.

@ShubhamOulkar ShubhamOulkar requested a review from a team as a code owner September 20, 2025 15:05
Copy link

netlify bot commented Sep 20, 2025

Deploy Preview for expressjscom-preview ready!

Name Link
🔨 Latest commit eecff84
🔍 Latest deploy log https://app.netlify.com/projects/expressjscom-preview/deploys/68cec951e95c370008205c39
😎 Deploy Preview https://deploy-preview-2063--expressjscom-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Contributor

github-actions bot commented Sep 20, 2025

🚦 Lighthouse Results (Mobile & Desktop)

URL Device Perf A11y Best Practices
/ mobile 🟠 76 🟢 100 🟢 93
/en/blog/posts.html mobile 🟢 96 🟢 96 🟢 93
/en/5x/api.html mobile 🟠 79 🟢 95 🟢 93
/ desktop 🟠 76 🟢 100 🟢 93
/en/blog/posts.html desktop 🟢 99 🟢 96 🟢 93
/en/5x/api.html desktop 🟢 90 🟢 95 🟢 93

Copy link
Member

@jonchurch jonchurch left a comment

Choose a reason for hiding this comment

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

This PR is big (59 files), alters files being moved, has diffs in the moved files, and the. There is no explanation for these changes.

The linked Jekyll tutorial does not recommend this restructuring, and there’s no explanation provided for why it’s being done.

@jonchurch
Copy link
Member

Before I would approve a PR like this, it would need to be limited to the changes required to achieve the goal. So no extraneous diffs.

I would also want a compelling reason for touching so many files in the first place.

Otherwise it looks like rearranging the furniture for no reason, and Id be inclined to close the PR.

@ShubhamOulkar
Copy link
Member Author

@jonchurch Thanks for the review! This will really help us manage website assets more gracefully, and it’ll make things much smoother if we ever redesign the site or migrate to a new platform. It improves DX and avoids unnecessary root clutter. Kind of like furniture—you can only use it if it’s arranged properly. 🫠

@ShubhamOulkar
Copy link
Member Author

we ever redesign the site or migrate to a new platform

his PR is big (59 files), alters files being moved, has diffs in the moved files

This PR is quite big (59 files), and it touches both moved files and their diffs. But I’d also point out that if we ever do a migration, the diffs will end up being even bigger than this. I’d like to avoid that scenario, since larger diffs usually lead to more mistakes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants