Docs: Work with content-scope-scripts repo on Windows

[jonathanKingston]

Asana Task/Github Issue: https://app.asana.com/1/137249556945/project/1201614831475344/task/1210717003881747?focus=true

Description

Move content from: Work with content-scope-scripts repo on Windows

Testing Steps

Checklist

Please tick all that apply:

• I have tested this change locally
• I have tested this change locally in all supported browsers
• This change will be visible to users
• I have added automated tests that cover this change
• I have ensured the change is gated by config
• This change was covered by a ship review
• This change was covered by a tech design
• Any dependent config has been merged

[netlify]

✅ Deploy Preview for content-scope-scripts ready!

Name	Link
🔨 Latest commit	8c955ca
🔍 Latest deploy log	https://app.netlify.com/projects/content-scope-scripts/deploys/686c42db6322290008ecca80
😎 Deploy Preview	https://deploy-preview-1794--content-scope-scripts.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

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

[github-actions]

Temporary Branch Update

The temporary branch has been updated with the latest changes. Below are the details:

• Branch Name: pr-releases/pr-1794
• Commit Hash: e9ee5a276a48162f3e07cb68e5903bff89f670ef
• Last Updated: July 7, 2025 at 9:58:21 PM UTC
• Install Command: npm i github:duckduckgo/content-scope-scripts#e9ee5a276a48162f3e07cb68e5903bff89f670ef

Please use the above install command to update to the latest version.

[github-actions]

[Beta] Generated file diff

Time updated: Mon, 07 Jul 2025 21:58:42 GMT

[shakyShane]

I don't mind having a 'recommendation' for WSL, but I wouldn't want us to get closer to codebases like the extension where the continued use of bash has made it difficult for FE/JS folks to contribute to. Node is cross-platform by default and we should lean on it IMO - that's how you make contribution on Windows easier. Requiring WSL is the opposite, it's a more complicated contribution path :) Maybe we just change the wording or something to indicate 'you might prefer WSL' and not 'you can only build with WSL'?

[jonathanKingston]

mmendation' for WSL, but I wouldn't want us to get closer to codebases like the extension where the continued use of bash has made it difficult for FE/JS folks to contribute to. Node is cross-platform by default and we should lean on it IMO - that's how you make contribution on Windows easier. Requiring WSL is the opposite, it's a more complicated contribution path :) Maybe we just change the wording or something to indicate 'you might prefer WSL' and not 'you can only build with WSL'?

Yeah happy to make this change, BTW I think the Windows devs wrote this: https://app.asana.com/1/137249556945/project/1201614831475344/task/1203837324583081?focus=true

[jonathanKingston]

@shakyShane OK I've made it a suggestion along with the other bits. I think this sort of highlights orphaned docs like this in Asana and how outdated they get. I think some of the other advice is worth having anyway.

My view is we can continue to iterate here and AI tools are likely to find silliness faster too.