# Sources of Information Most information that you will find on React is written or created in English. Even developers that do not speak English as their native language often write articles or blogs in English in order to reach a broader audience. At the same time, it is very important to provide materials for those who cannot speak or understand English quite as well as their native language. So if you do speak another language, give it a try and provide information in your native language too! For me, that was the primary driver to publish this book in German as I could make it more accessible to German developers. Most of the material that I will mention in the course of this section will be in English though. ## Twitter Twitter is a great source of information for current trends in the tech community. The React Team even announces their changes publicly on Twitter very shortly after releasing them. If you do not have an account yet, but like to stay up to date, you should think about creating an account for yourself and checking in every now and then to make sure you are getting the most relevant content. I will try and name a few accounts that I have found invaluable when it comes to working with React and who generally tweet on the topic. This list is not exhaustive by any means though and I know that there are a great number of other people who also do great work in the React space. I do however follow these people myself and can therefore wholeheartedly recommend them: [@reactjs](https://www.twitter.com/reactjs) [@dan\_abramov](https://www.twitter.com/dan_abramov) [@sophiebits](https://www.twitter.com/sophiebits) [@sebmarkbage](https://www.twitter.com/sebmarkbage) [@acdlite](https://www.twitter.com/acdlite) [@brian\_d\_vaughn](https://www.twitter.com/brian_d_vaughn) [@trueadm](https://www.twitter.com/trueadm) [@threepointone](https://www.twitter.com/threepointone) [@aweary](https://www.twitter.com/aweary) [@necolas](https://twitter.com/necolas) [@tomocchino](https://twitter.com/tomocchino) [@yuzhiz](https://twitter.com/yuzhiz) [@rachelnabors](https://twitter.com/rachelnabors) [@lunaruan](https://twitter.com/lunaruan) (all React core members or alumni) [@ryanflorence](https://www.twitter.com/ryanflorence) [@mjackson](https://www.twitter.com/mjackson) [@ken\_wheeler](https://www.twitter.com/ken_wheeler) [@kentcdodds](https://www.twitter.com/kentcdodds) [@kyleshevlin](https://www.twitter.com/kyleshevlin) [@mweststrate](https://www.twitter.com/mweststrate) [@jaredpalmer](https://www.twitter.com/jaredpalmer) [@sebmck](https://www.twitter.com/sebmck) [@thekitze](https://www.twitter.com/thekitze) [@PhilippSpiess](https://www.twitter.com/PhilippSpiess) [@monicalent](https://www.twitter.com/monicalent) [@nikkitaftw](https://www.twitter.com/nikkitaftw) [@rwieruch](https://www.twitter.com/rwieruch) [@jlongster](https://www.twitter.com/jlongster) [@eveporcello](https://www.twitter.com/eveporcello) [@vincentriemer](https://www.twitter.com/vincentriemer) [@kylemathews](https://www.twitter.com/kylemathews) [@rauchg](https://www.twitter.com/rauchg) [@erinfoox](https://www.twitter.com/erinfoox) [@jevakallio](https://www.twitter.com/jevakallio) [@okonetchnikov](https://www.twitter.com/okonetchnikov) [@manuelbieh](https://www.twitter.com/manuelbieh) [@manjula\_dube](https://www.twitter.com/manjula_dube) [@acemarke](https://www.twitter.com/acemarke) [@wisecobbler](https://www.twitter.com/wisecobbler) [@mxstbr](https://www.twitter.com/mxstbr) [@cpojer](https://www.twitter.com/cpojer) [@lithinn](https://www.twitter.com/lithinn) [@dabit3](https://www.twitter.com/dabit3) [@saifadin](https://www.twitter.com/saifadin) [@rickhanlonii](https://www.twitter.com/rickhanlonii) [@tylermcginnis](https://www.twitter.com/tylermcginnis) [@wesbos](https://www.twitter.com/wesbos) [@\_developit](https://www.twitter.com/_developit) [@ProvablyFlarnie](https://www.twitter.com/ProvablyFlarnie) [@emmabostian](https://www.twitter.com/emmabostian) [@grabbou](https://www.twitter.com/grabbou) [@cassidoo](https://twitter.com/cassidoo) ## Newsletters Don't worry, I'm not referring to those kind of newsletters that constantly try to sell stuff to us. Luckily, the React community has a number of very interesting, cared for and nicely designed newsletters which are well worth subscribing to. Most of these newsletters are sent out on a weekly basis and contain a great overview of what has happened in the React World in the previous week. A great choice for all those who find Twitter a little bit too fast-paced or stressful: * [React Status](https://react.statuscode.com/) (Peter Cooper / Cooperpress) * [This Week in React](https://this-week-in-react.org/) (Philipp Spiess) * [React.js Newsletter](http://reactjsnewsletter.com/) (Tyler McGinnis) * [Fullstack React](http://newsletter.fullstackreact.com) (Sophia Shoemaker) * [React Digest](https://reactdigest.net/) (Jakub Chodounsky / Bonobopress) * [Tiny React](https://tinyreact.email/) (Siddharth Kshetrapal) ## Communities * * * ## Podcasts There are a few very good podcasts which mainly cover React topics: * [The Undefined](https://undefined.fm/) (Ken Wheeler and Jared Palmer) * [React Podcast](https://reactpodcast.com/) (Michael Chan aka @chantastic) * [Syntax.fm](https://syntax.fm/) (Wes Bos and Scott Tolinski) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://learn.react-js.dev/ecosystem/sources-of-information.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.