new` page

Needs Translation

Created on March 5, 2026 , translate by Sunday, March 8, 2026 (in 2 days)

Translate 1 original (10 words) to Turkish Glossary

Prio	Original string	Translation	—
	Sorry, we couldn't find any sites related to your search.	You have to log in to add a translation.	Details
Sorry, we couldn't find any sites related to your search. Sorry, we couldn't find any sites related to your search. You have to log in to edit this translation. or Cancel Translation Memory Loading… Meta Status: untranslated Priority: normal More links: Permalink to this original All translations of this original Show all translations across locales Show original across locales Show all deliverables with this original (tr) Show all deliverables with this original (overview) View deliverable: Reader: Show Related sites on the `/reader/new` page

Legend:

Current

Waiting

Fuzzy

Old

With warnings

Export strings as

Show a list of non-subscribed sites when the user inputs a site or any value on the new /reader/new page
Code improvements to reduce codebase complexity and simplify the sync between /reader/new and reader/subscriptions

Remove UnsubscribedFeedsSearchProvider and useUnsubscribedFeedsSearch
- useUnsubscribedFeedsSearch is exactly the same as useReadFeedSearchQuery with unused complexity, like handle pages
- UnsubscribedFeedsSearchProvider react query already has a context to share data across the app, making the provider useless.
Replace ‘wpcom-proxy-request’ bycalypso/lib/wp due to issues with running the code inside the test suite (Node env)

Go to /reader/new
type any value (E.g. gato) in the Add new sites, newsletters, and RSS feeds to your reading list input
Check you can see a list of Related sites based on what you typed.

Has the general commit checklist been followed? (PCYsg-hS-p2)
Have you written new tests for your changes?
Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
Have you checked for TypeScript, React or other console errors?
Have you tested accessibility for your changes? Ensure the feature remains usable with various user agents (e.g., browsers), interfaces (e.g., keyboard navigation), and assistive technologies (e.g., screen readers) (PCYsg-S3g-p2).
Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
Have we added the “[Status] String Freeze” label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
- For UI changes, have we tested the change in various languages (for example, ES, PT, FR, or DE)? The length of text and words vary significantly between languages.
For changes affecting Jetpack: Have we added the “[Status] Needs Privacy Updates” label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

Unfortunately, no screenshots were provided by the developer.