[Suggestion]: Don't reference blog post from legacy site
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11.8k
- Forks
- 7.9k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 11
Description
Summary
On Writing Markup with JSX page, legacy blog post is referenced.
Page
https://react.dev/learn/writing-markup-with-jsx#jsx-putting-markup-into-javascript
Details
It would be great to migrate this blog post to the new site, because legacy site is not maintained anymore.
Since I'm working on Serbian translation, and legacy site doesn't have Serbian version, my fellow countrymen can be deprived of reading this post on their mother tongue.
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 with the JSX section on the Writing Markup with JSX page and read the linked legacy blog post, especially the referenced anchor. Migrate the relevant blog content to the new site, update the page so it no longer references the legacy site, and verify the Serbian translation can use the new-site version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100