The News Hub Is an Architecture Decision, Not a Content Decision

Religion News Service just raised $1 million to build a news hub around one specific intersection: faith and immigrant communities. The project is called An Atlas of American Belonging. Their first move was to partner with El Paso Matters, a local nonprofit newsroom with deep roots in a border community where Catholicism and immigration are not two topics sitting next to each other but the same story told in different registers.

That framing is worth slowing down on. Not because the journalism isn't important (it is), but because the structural decision underneath it is something most newsrooms skip entirely.

A beat is not a hub

Most newsrooms that cover immigration treat it as a beat. Reporters file stories. Stories go on the homepage or into a section. Readers find them through search or a newsletter and then leave. There is no architecture pulling the coverage together into something a reader can return to, navigate through, or share as a coherent body of work.

A hub is different. A hub is built around an intersection, a community, a question that stays open. Faith and immigration is an intersection. Belonging as a contested American concept is a question that stays open. Those are things readers can have a relationship with over time, not just a story they click once.

That distinction changes everything about how you build the thing. A beat lives in a CMS category. A hub needs taxonomy, cross-linking logic, landing page architecture, and a clear answer to the question: what does a reader do here after they finish one story?

The architecture problem most newsrooms ignore

When I work with newsrooms on their sites, the content strategy conversation almost always comes before the web architecture conversation. Editors decide what they want to cover, and then they ask someone to build a page for it. The page ends up being a reverse-chronological list of articles with a headline at the top. That is not a hub. That is a tag page with better branding.

A real hub answers a few specific questions through its design. What is this place about, in one sentence, for someone who has never heard of your newsroom? What is the connective tissue between stories, and can a reader see it without reading every piece? What can a first-time visitor do here besides read one article and leave?

Those are web architecture questions. They require decisions about page templates, internal linking patterns, content types beyond the article, and how the hub relates to the rest of the site. They also require editorial decisions that most newsrooms push off: What is the core frame? What is in scope and what is not? Who is this for, specifically?

A recent piece on the Atlas of American Belonging quotes RNS editorial director Pam Kruger saying the hub will "enable people to make connections between stories and see trends that maybe an individual story wouldn't necessarily point to." That is a design goal, not just an editorial one. It requires building something that surfaces connections, not something that publishes articles.

Why community intersections outperform broad beats

Faith and immigration is specific enough to be useful to a reader. Immigration alone is too broad to build identity around. Faith alone reaches a general audience that may not care about the immigration angle. The intersection is where the audience lives, and it is also where the editorial distinctiveness lives.

Documented covers immigration in New York with a focus on immigrant communities themselves as the primary audience. El Tímpano covers Latino communities in the Bay Area, with deep investment in Spanish-language and audio content. Both of those are intersections, not beats. The specificity is the point. It tells a reader: this is for you, this is about your world, and we are not going to dilute it to appeal to everyone.

That specificity is also what makes a hub shareable. People share things that feel like they were made for a community they belong to. A well-framed hub with a clear identity travels through those communities in ways that a generic immigration section never will.

What to actually build

If you are thinking about organizing coverage around a community intersection, the content decision and the architecture decision need to happen at the same time. Before you assign stories, answer these questions at the site level. Where does this hub live, and how does a reader get there? What exists on the hub page beyond a list of articles? How does a story in this hub link back to the hub and to related stories, not just to the homepage? What is the email or return path for someone who finds one piece and wants more?

The journalism RNS is doing matters. The model they are building around it is what will determine whether it compounds over time or stays flat. That part is a web problem. Solve it like one.