JENNIFER GUTIERREZ Discuss a project

Research websites

Websites built around the science and the people who need to use them.

Custom websites and complete rebuilds for PIs, labs, centers, programs, consortia, societies, and research nonprofits. The structure, content, design, update path, and hosting plan are defined together.

Current content Research, people, publications, or opportunities are out of date.

Research themes, people, publications, and opportunities need a clearer structure.

Updates are difficult The team needs a clear update process.

A practical editor or defined update process can be part of the build.

The audience has changed Recruitment, collaboration, or public information now matters.

The site can be organized for the people who actually need to use it.

A focused lab site or a larger research publication system.

The project is shaped around the content and workflow. It can be a concise PI or lab site, a multi-institutional consortium site, a program or center website, or a digital publication with structured records and editorial stories.

01

PI and lab websites

Research focus, people, publications, news, opportunities, contact information, and a clear update path.

02

Program and consortium sites

Investigators and partner sites, shared programs, resources, working groups, updates, and collaboration information.

03

Centers and societies

Audience-specific navigation, programs, membership or participation information, news, events, and resources.

04

Reports and research publications

Annual reports, research highlights, donor impact microsites, story collections, and structured publication or funding records.

Examples include lab, consortium, annual report, impact-reporting, and research-story websites.

The public examples use changed or created names, institutions, data, and identifying details. They are examples of project types and are not presented as client work.

Explore research website examples →

Design, content, updates, hosting, and handoff are part of the same plan.

  1. 01
    Define the audience and content

    Clarify who the site serves, what information must be easy to find, and what already exists.

  2. 02
    Develop the structure and visual direction

    Build a content architecture and design system specific to the field, program, and organizational context.

  3. 03
    Choose the update path

    Use a content editor, a documented handoff, or ongoing support based on how the team works.

  4. 04
    Set the hosting boundary

    Use an existing domain or a hosted researchpages.org address. Ownership, security, maintenance, and ongoing costs are written into the scope.

Research website questions

Can a research team update the site after launch?

Yes. A content editor can support routine changes such as publications, people, news, and opportunities. A complete handoff or ongoing support can also be defined.

Can the website use an existing domain?

Yes. A project can use an organization-owned domain or a hosted project address at researchpages.org.

Can you work with a group outside the United States?

Yes. Projects can support research groups and scientific organizations based in or outside the United States.

Every project begins with a written scope and estimate covering the build, content responsibilities, hosting, editor access, maintenance, and update process.