Aller au contenu principal

This Week In React - Editorial line

This Week In React is a weekly curation newsletter for mid/senior React and React Native developers. This page explains how we select the links of each issue.

It also explains why a link you submitted, or a project you'd like us to cover, might not appear in the newsletter. That doesn't mean it isn't good: it just doesn't match what we want to offer our readers.

Our goal​

We want to be the pulse of the React ecosystem, not a discovery tool for every React npm package.

The ecosystem is thriving, so each issue contains a lot of links. Instead of filtering links more aggressively, we optimize for a good reading experience despite the information density: consistent, easy to scan, with the information "inlined" whenever possible. Reading the newsletter should provide value without clicking a single link. We don't want to bait you into clicking a link and then disappoint you.

What we look for​

  • Fresh content. One month is already old: we probably covered it.
  • Event-driven content, such as a new release, a new project or a new docs page.
  • Weak signals that help understand what the future will look like.
  • Content focusing on a single idea, explaining a concept in depth.
  • Content focusing on React core techniques, broadly applicable by a large audience.
  • Content presenting novel, innovative or underrated techniques.
  • Content covering niche topics and weak signals, when well presented or impactful.
  • Content with an outstanding presentation effort and a great reading experience, such as interactive articles.
  • Tools and libraries that developers can use for free, in a platform-agnostic way.

What we filter out​

  • Product news: launches and features tied to a single vendor, a single platform or a paid plan.
  • Content teaching how to use a paid product, unless it isn't too promotional and teaches something valuable about React along the way.
  • Content produced by AI, SEO listicles and other low-quality articles.
  • Content behind a paywall, requiring an account, or with a bad reading experience.
  • Content for junior developers: 101s, step-by-step tutorials, paraphrased official docs with no added value.
  • Most UI libraries and boilerplates: there are simply too many. Exceptions: high traction, a long-term maintenance commitment, or an authority behind them. We don't cover their launch, but we might cover their v10 once it's mainstream and has proven its value to the community.
  • Weak signals that are too weak: if we can't explain their impact in simple words, or if only a dozen people would benefit, it's probably too soon.
  • Releases with nothing interesting to highlight, which is often the case for patch releases.
  • X/Twitter threads and conversations, which require an account to read. We prefer external links. A single post is fine when it contains all the information, a link or a video demo.

We can always make exceptions for content with an outstanding presentation effort. For example, an interactive article explaining basic React concepts is fine: our readers might share it with their junior colleagues.

Sections​

  • Intro: a short recap of the week's news.
  • ⚛️ React: content relevant to all React devs, and to React web devs. It has to be about React itself: projects that borrow ideas from React without being React don't belong there.
  • 📱 React Native: content relevant to React Native devs, including Expo and the native platform news that affects React Native apps.
  • 🔀 Other: content relevant to a broader JavaScript audience: TypeScript, CSS, HTML, TC39, tooling and more. We keep this section short.
  • 🤭 Fun: 1–3 memes or fun screenshots, preferably about React and the news of the week.

This page is about our organic content. Sponsored content is marked with 💸. If your content doesn't match our editorial line, a sponsorship can still be a way to reach our readers.