[website] Support the forward of utm_source in the /careers/ job pages to Ashby
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 99.1k
- Forks
- 32.5k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 106
Description
Summary
Right now, we link the job in Ashby directly when we need to track the origin, e.g. https://www.notion.so/mui-org/Talent-acquisition-0a660e7659e5494587237ef3e417c4cd?pvs=4#afa2be5f80474b26bba0d8382c3ac8db. It would be much better if instead of linking https://jobs.ashbyhq.com/MUI?utm_source=Xnzy3Q3MGR we could link https://mui.com/careers/?utm_source=Xnzy3Q3MGR#open-roles without losing the source.
Examples
No response
Motivation
No response
Search keywords: -
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the /careers/ job pages and trace how links to Ashby are constructed. Verify the implementation preserves the utm_source value when navigating through the careers page, including the #open-roles anchor, and confirm the resulting Ashby URL retains that source.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100