We’ve seen state encapsulated within components, lifted to shared parents, in form fields, persisted across renders, and pulled in from a database, and we’ve used a whole bunch of hooks to help us set up and work with that state. Our approach has been to keep the state as close to the components that use it as possible. But it’s not uncommon for many components, nested on multiple branches, to hunger for the same juicy worms, the same tidbits of application state, like themes, localization info, or authenticated user details. Mmmmmmm, tidbits . . . React’s Context API is a way of delivering juicy state tidbits directly to your nest without passing them down through multiple layers of intermediaries who, preferring tacos to tidbits, have no interest in them.