Frequently Asked Questions

Good newsroom branding is not the logo. It is the consistent way your reporting, your visuals, and your voice show up across the homepage, the newsletter, the donation page, and your social posts. When a reader recognizes you in two seconds, your branding is doing its job. When they wonder if they landed on the right site, it is not.

Start with the work. The kind of journalism you publish, who you publish it for, and what your reporting feels like when read aloud. Every visual decision (typography, color, photo treatment, microcopy) should echo that. A site that reads like the newsroom is one a reader can trust before they finish the first story.

Because readers do not visit a newsroom to fight the interface. They visit to read, understand, and share. Good UX gets out of the way: stories load fast, navigation is obvious, donations take three taps instead of nine. Bad UX puts friction in front of the journalism, and friction is the leading cause of bounce.

Editorial voice is how the newsroom sounds when no one is editing for tone. It lives in headlines, newsletter intros, button text, and error pages. We find your voice by listening to your existing work, then writing guidelines so it shows up consistently whether the writer is the editor-in-chief or a freelance contributor.

A clear wordmark that holds up at favicon size. A type system that handles both long-form reading and short-form social. A color palette that does not fight your photography. A voice guide your reporters will actually use. And a clear position: who you cover, who you do not, and why.

Because inconsistency breaks trust faster than anything else. If the homepage feels rigorous and the newsletter feels like a different publication, readers wonder which voice is real. Consistency is not about being boring, it is about being legible to the people who decide whether to support the work.

Design is how the page looks. Branding is the underlying decision about why it looks that way. Good newsroom design without branding is decoration. Good branding without design is a deck nobody reads. They have to work together to support the journalism, not compete with it.

Three signals: readers cannot find recent stories without scrolling forever, the donation page converts worse than a Google Form would, or the site does not load on a phone with bad signal. If two of those are true, you are likely past due. If all three are true, the cost of waiting is bigger than the cost of rebuilding.

A focused redesign typically runs 8 to 14 weeks. A full custom newsroom website with editorial CMS, donation flow, and member portal is usually 4 to 6 months. Faster than that means cutting corners. Slower means the scope is wrong. We work backwards from real deadlines like NewsMatch or election windows.

Start with one clear sentence about what the new site has to do better than the current one. Define the audience, list the must-haves, and ruthlessly cut the maybe-laters. Then pick a partner who treats your scope like their own constraint. The unknown becomes manageable when the goals are honest.

A working conversation, not a sales pitch. We look at your site, your donor flow, your traffic, and what your team is wrestling with. You leave with a clear opinion on what to fix first and what to leave alone. Sometimes that opinion is 'do not redesign right now,' and we will say that.

Newsrooms cannot afford vanity projects. Honest feedback at the start saves the budget that would have funded a rebuild you did not need. When we push back on a feature or a scope expansion, it is because we have seen what happens when those decisions go unchecked. Better a hard conversation in week one than an awkward one in month six.

Strong structure is what lets creativity ship. We start with constraints: CMS workflow, performance budget, accessibility floor. Then design can push within those edges without breaking. The result is a site that feels distinctive but does not collapse the first time a reporter publishes a long-form piece on deadline.

Because every newsroom we have worked with has been doing something differently from the last one. The donation funnel that worked for an investigative outlet does not always work for a community-news outlet. The CMS that suits a daily does not always suit a quarterly. Listening first means we recommend what fits, not what we already built.

Reader trust drops, and trust is the asset non-profit newsrooms cannot afford to lose. A homepage that feels rigorous and a social account that feels frantic make readers wonder which voice is real. Members start hesitating. Donors start asking more questions. Consistency is not aesthetic, it is operational.

News SEO is different. Search engines treat journalism differently from generic content: news schema, freshness signals, author authority, and structured data for articles all matter more. We start by mapping what your readers actually search for, then build the technical structure that lets your stories surface when they do.

We do not chase keywords that do not match your mission. We do not run link-building campaigns that contradict your editorial standards. We focus on what moves newsroom traffic: technical health, accurate news schema, author pages that signal expertise, and retention metrics that prove readers are coming back.

Start with the problem the newsroom is trying to solve, not the feature you want to build. A reader-callout tool, a data dashboard, a multilingual section, a custom investigation site. We help you scope the minimum version that proves the value, ship it, and decide whether to keep going. Most newsroom side-projects fail because they were never small enough to start.

Often, just updates. A faster homepage, a better donation page, cleaner navigation, working search. Those changes can move the numbers as much as a full redesign at a tenth of the cost. We audit before we propose, and if a partial fix is the right answer, that is what we will say.

Vendor-agnostic, every time. WordPress, custom CMS, headless, static, hybrid. What matters is whether your editorial team can actually use it on deadline. We recommend what fits your workflow, your budget, and your future, not what we are most comfortable with or what we resell.

We design and build to WCAG 2.1 AA at minimum. Real alt text for photos and infographics, keyboard navigation, screen-reader-friendly story structures, color contrast that works for low-vision readers, and content that does not assume a fast connection. Accessibility is not a checklist for newsrooms, it is who reaches the journalism.

It means the technology serves the journalism, not the other way around. We do not pitch features because they are clever, we recommend them because they make the work easier to publish, easier to find, easier to fund. When the tech disappears and the reporting is what readers remember, the tech is doing its job.

We are small, direct, and we have spent years inside non-profit newsroom budgets. We will tell you when a feature is not worth building. We will push back when scope creep would compromise the launch. And we will be on the other end of an email when something breaks at 6 a.m. on election day. We are partners, not vendors.

Yes, and often that is the highest-leverage work. A performance audit usually surfaces fixes that double load speed without rebuilding anything: image optimization, caching, third-party script audits, render-blocking removal. Stories that loaded in six seconds suddenly load in two. Readers stay, and Google notices.

Yes, exclusively. We made the deliberate choice to focus on non-profit newsrooms and independent journalism. Constrained budgets and clear missions produce better work, and after years of doing both kinds of projects, this is the kind we want to do.

Two to four weeks of structured conversations and analysis. We talk to editors, reporters, the audience team, the development director, and whoever wears the IT hat. We audit the site, the analytics, the donor data, the publishing workflow. We surface risks early. By the end you have a written plan, a real budget, and a launch date that is not aspirational.

Lean code, optimized images, smart caching, minimal third-party scripts, and a CMS that does not generate bloated markup. Fast is not just for Google: it is the difference between a reader finishing your story and bouncing because the photo gallery took nine seconds to render. Speed is a mission-critical metric for journalism.

Yes. We help newsrooms move past pageviews to the metrics that actually matter for journalism: returning readers, story completion rates, newsletter signup rates, donation conversion paths. Numbers should answer questions, not generate noise. We make the data legible so the editorial team can act on it.

We build multilingual sites that feel native in every language, not auto-translated. Real editorial structure, language-specific URL paths, hreflang setups that search engines respect, and workflows that let a Spanish-language reporter publish without going through an English-first review. Multilingual journalism deserves multilingual infrastructure.

We offer ongoing maintenance plans: security updates, performance monitoring, content support, and quick-turn help when something breaks. But we also document everything so any developer can pick the work up. The newsroom owns the code, the donor data, and the documentation. We stay close because we want to, not because you have no other choice.