Museum websites: plan the visit before the visual effect

A museum website should first help someone decide whether, when, and how to visit. Put reliable hours, admission information, location, and access details ahead of visual effects. Collections and exhibition storytelling still matter, but they should not conceal the facts a person needs before leaving home.

Organize around visit decisions

Separate a first-time visit from a return visit, school inquiry, or collection research task. These journeys overlap, but they do not begin with the same questions. A person planning today needs current opening information. A teacher needs group arrangements and a response channel.

Keep “Plan your visit” reachable from exhibition pages, not only the homepage. Use descriptive menu labels and indicate the current location. W3C’s menu structure tutorial explains menu labeling and current-item markup. These mechanisms support orientation without requiring visitors to interpret the institution’s internal department names.

Give operational facts an owner

Opening hours, exceptional closures, admission conditions, and available facilities need assigned editors and review rules. A beautifully designed hours page is harmful if an unreviewed exhibition page contradicts it.

Maintain one authoritative record for shared visit facts and reuse it where possible. Model exhibition dates separately from daily opening hours: an exhibition running through a month does not imply the building opens every day of that month. Include temporary access changes with a clear expiry or review date.

For the Joslyn project, 5e Labs used a Next.js frontend and a WordPress backend in 2024. In that kind of split architecture, the general implementation question is how an approved CMS change reaches the public interface. A preview alone cannot establish that today’s closure notice is visible to visitors.

A hypothetical visitor planning a weekend trip

Imagine a family visiting San José for a weekend, including a person who needs step-free access. This is a hypothetical journey, not a description of a particular museum. Before traveling, they need to know:

Question	Information the website should supply
Can we visit on that date?	Hours and exceptional closures
What does admission involve?	Current conditions and booking requirements
Which entrance should we use?	Arrival and access details
Will the exhibition still be open?	Exhibition dates distinct from building hours
Who can answer an unresolved need?	A working contact route

If the access information only says “accessible,” the family still cannot plan. Publish verified details about routes and facilities, and provide a contact for needs the page cannot answer. Avoid promising conditions that staff have not checked.

Test the ticket handoff and the return path

When admission uses another system, check that dates, language, and selected ticket details remain understandable across the handoff. Test unavailable dates, cancellations, and a return to the museum site. Explain the next step when booking is unnecessary or unavailable instead of leaving a dead button.

Review the journey on a phone outdoors and with keyboard navigation. Keep maps useful without making a map the only source of the address or entrance instructions. Large imagery should add inspection value rather than delay access to practical details.

Ask someone unfamiliar with the institution to plan a visit using only the current website. Record every unanswered question, then assign an owner to the missing facts. Use that list as the brief for a UX/UI design review with 5e Labs, and repeat the visit-planning task after the changes.