Skip to content
WilliamAlexander.co
  • Studio
  • Work
  • Services
  • Process
  • Writing
  • Lab
  • About
  • Start a project
  1. Home
  2. Articles
  3. Faculty Website Redesign: A Survival Guide
Higher Ed Web

Faculty Website Redesign: A Survival Guide

Working with professors who have strong opinions about their web presence

July 4, 2026 10 min read

Key Takeaways

  • Understand academic culture and faculty priorities before starting
  • Provide meaningful choices within university constraints
  • Make the update process as simple as possible
  • Work with department coordinators, not just faculty directly
  • Plan for varying levels of technical skill and engagement
Overview

The Faculty Website Challenge

Faculty websites occupy a peculiar space. They represent individual academics with international reputations and strong personal brands, but they also represent the university and must meet institutional standards. Faculty are experts in their fields but rarely in web design. They want control but often won't invest time in maintenance.

Redesigning faculty websites means navigating these tensions. Done well, you create profiles that serve both faculty goals and student needs. Done poorly, you create frustrated academics and abandoned web pages.

Respect the Expertise

Faculty have spent decades building expertise and reputation. Approach their web presence with that respect. You're helping them present their work effectively, not imposing design decisions. The partnership framing changes everything.

Priorities

Understanding Faculty Priorities

Faculty care about different things than marketing departments.

What Faculty Want

  • Research visibility: Publications, grants, and recognition
  • Academic reputation: How they appear to peers
  • Student recruitment: Attracting graduate students
  • Time efficiency: Minimal effort to maintain
  • Academic freedom: Control over their presentation

What Faculty Often Overlook

  • Undergraduate student needs
  • Accessibility requirements
  • Mobile experience
  • University brand consistency
  • Outdated content cleanup

Faculty Segments

Not all faculty have the same needs:

Faculty Type Primary Concern Web Priority
Research-focused Publication visibility CV, publications list, lab info
Teaching-focused Student resources Course materials, office hours
Public scholars Media presence Talks, commentary, media links
Administrators Official duties Role description, contact info
New faculty Establishing presence Basic profile, building content
Design

Design Approach

Template-Based Flexibility

Create templates that offer meaningful choices:

  • Layout options (emphasis on research vs. teaching)
  • Content sections that can be shown or hidden
  • Profile photo options (formal vs. candid)
  • Customizable secondary content areas

Required vs. Optional Sections

  • Required: Name, title, department, contact info, photo
  • Recommended: Bio, education, research interests
  • Optional: Publications, courses, awards, media, personal statement

Publications Integration

Publications matter most to faculty. Make this section excellent:

  • Import from ORCID, Google Scholar, or institutional repository
  • Proper citation formatting
  • Links to PDFs where possible (respecting copyright)
  • Easy manual additions for recent work

Automatic Updates

Where possible, pull data automatically. Integration with CV systems, publication databases, or institutional data reduces faculty maintenance burden and keeps profiles current.
Engagement

Working With Faculty

Initial Outreach

  1. Work through department coordinators

    Coordinators know faculty schedules and preferences. They can facilitate introductions and follow-up.

  2. Frame the benefit clearly

    Lead with what faculty gain: better visibility, student recruitment, reduced maintenance.

  3. Offer multiple engagement options

    Some want hands-on involvement; others want to submit content and be done.

  4. Set clear timelines

    Academic schedules are predictable. Plan around teaching loads and sabbaticals.

Communication Strategies

  • Keep emails brief and specific
  • Respect that faculty email volume is enormous
  • Provide clear deadlines with consequences
  • Follow up through multiple channels if needed
  • Use department meetings for announcements

Handling Resistance

  • "I don't have time": Offer to build profile from existing materials
  • "I like my old site": Explain accessibility/mobile requirements, offer migration help
  • "I want it to look different": Explore options within templates, explain brand standards
  • "Why do I need this?": Share data on student use, peer institution examples
Content

Content Collection

Making It Easy

  • Provide forms with clear fields
  • Accept content in any format (Word, PDF, plain text)
  • Offer to interview faculty and write their bio
  • Pull from existing materials (CVs, department directories)

Photo Requirements

Faculty photos are surprisingly contentious:

  • Offer professional photo sessions (scheduled at their convenience)
  • Provide clear specifications if they supply their own
  • Allow some variety (lab settings, outdoor shots) within guidelines
  • Have a graceful fallback if they refuse photos

Bio Writing

Faculty bios vary wildly in quality. Options:

  • Provide a template structure
  • Offer professional writing assistance
  • Show examples of effective bios
  • Review and edit submitted content

The CV Approach

Most faculty have CVs they maintain carefully. Offer to build their profile directly from their CV. This respects their existing work and reduces redundant effort.

Graduate Student Help

Grad students often know faculty research well and can help gather and organize content. Some may appreciate the opportunity. Just ensure faculty approve the final content.

Technical

Technical Considerations

Editing Interface

Faculty technical skills vary enormously:

  • Some are comfortable with code; most aren't
  • Simple, intuitive editing interfaces are essential
  • Preview functionality reduces errors
  • Clear save/publish workflow

Mobile Considerations

  • Faculty rarely check their own sites on mobile
  • Students absolutely do
  • Responsive templates are non-negotiable
  • Test with common student devices

Accessibility

  • University legal obligation regardless of faculty preference
  • Build accessibility into templates
  • Provide guidance on accessible content (alt text, document formatting)
  • Audit for common issues

Legacy Content

Faculty often have years of accumulated files, links, and course materials. Plan for migration carefully. Some content is essential; much is obsolete. Work with faculty to identify what actually needs to move.
Maintenance

Ongoing Maintenance

Reducing Maintenance Burden

  • Automate where possible (publication feeds, course schedules)
  • Minimize required updates
  • Make updates quick and easy
  • Send targeted reminders (new publications, start of semester)

Support Structure

  • Clear documentation and help resources
  • Department-level support (trained coordinators)
  • Central web team for complex issues
  • Regular office hours or workshops

Governance

  • Define what happens when faculty leave
  • Establish content review schedules
  • Create process for handling outdated profiles
  • Balance faculty autonomy with institutional needs
Conclusion

Successful Faculty Websites

Faculty websites succeed when they serve faculty goals while meeting institutional requirements. That balance requires understanding what faculty actually care about, making participation easy, and providing meaningful flexibility within necessary constraints.

The web team's role is to be a partner, not an enforcer. Help faculty present their work effectively. Make the process as painless as possible. Build systems that don't require constant faculty attention. When you do that, everyone wins.

Frequently Asked Questions

How do I handle faculty who want complete design control?

Acknowledge their expertise in their academic field while explaining university web standards exist for good reasons—brand consistency, accessibility compliance, and user experience. Offer meaningful choices within those constraints. Frame it as professional partnership, not restriction.

What if faculty members won't respond to emails about their websites?

Faculty are often overwhelmed with email. Try different channels—department coordinators, in-person visits during office hours, or messages through department chairs. Set clear deadlines with consequences (site will launch with current content). Don't let one unresponsive person block the entire project.

Should faculty have their own websites separate from the university?

Many faculty maintain personal academic websites alongside university profiles. This is generally fine—encourage them to link between sites. The university profile should be consistent and maintained; personal sites can have more freedom. Just ensure official contact information appears on the university profile.

How do I get faculty to update their profiles regularly?

Make updates easy—simple interfaces, clear instructions, minimal required fields. Connect updates to things they care about: incoming students searching for advisors, grant committees looking at faculty credentials. Schedule annual reminder campaigns tied to academic calendar (before fall semester).
Higher Education Web Strategy Project Management Faculty Stakeholder Management
William Alexander

William Alexander

Senior Web Developer

25+ years of web development experience spanning higher education and small business. Currently Senior Web Developer at Wake Forest University.

Related Articles

Higher Ed Web

Redesigning Department Sites Without Chaos

10 min read
Higher Ed Web

Summer Website Projects for Universities

9 min read

Planning a faculty website redesign?

I help universities create faculty web presence strategies that work for both academics and institutions. Let's discuss your approach.

Let's talk about your project.

Send a few sentences about what you're working on. Start a project →

Practice

  • Work
  • Services
  • Web design
  • Process
  • Start a project

Read & explore

  • Writing
  • Lab
  • About
  • Resume

Elsewhere

  • LinkedIn
  • GitHub
  • Email

Based

Roanoke, Virginia
Working in Eastern Time

Selectively available, Q3 2026

© 2026 William Alexander. Built by hand in Roanoke, Virginia.

Set in Inter and Fraunces. Running on WordPress, hosted on Flywheel.