LFW

For arts & culture

A new season every few months. A website that keeps up.

A museum, theater, arts center, or library website changes as often as its calendar. Exhibitions open and close, classes fill, performances sell out, and the hours page is the most visited page on the site. All of it has to be right on a phone, on the day.

LFW hosts, maintains, and monitors arts and culture sites on WordPress. Your staff publish exhibitions, events, and news inside tested templates. Ticketing and membership stay with the systems you already use, and one monthly report goes to your director and your board.

Request a quote Book a call

Interactive example

An approval you can trace.

Review a change, complete its checklist, and move it to Ready.

Publishing desk
Review the change

Exhibition page

Current version

Dates: see the brochure PDF.

Proposed version

On view March 6 to June 14, with the opening reception on the calendar.

Before approval

3 checks remaining

Sample content. Changes stay in this browser.

30-minute tasks

Routine management, one task at a time.

1 day / 4 hours

Standard / Priority acknowledgment during business hours.

Fixed project quotes

Rebuilds, integrations, and larger work scoped separately.

Who handles what

Your program and your systems, on a platform LFW runs.

For marketing, communications, and operations staff at museums, performing arts organizations, arts centers, historical societies, arts councils, and libraries.

Your staff
Exhibition and program pages, event listings, hours and admission, images and their credits, news, and the words on every page.
Your vendors
Ticketing, class registration, membership, donations, and collections management stay with the systems you use. The website links to them and, where they offer it, reads their data.
LFW
Hosting, updates, security, daily accessibility monitoring, the events calendar, the monthly report, and routine changes such as a new exhibition template or a holiday hours banner.

From request to delivery

Put the calendar, the hours, and the images in order first.

The fixes that matter most are small and repeated: hours kept in one place, every image with a description and a credit, ticket and registration links that open in the same design, and the season brochure published as pages, not only as a PDF. None of that needs a redesign.

  1. Host and patch the platform

    Managed hosting for WordPress with staging, daily backups, and a firewall. Updates run monthly through staging, with security releases sooner. Image-heavy pages are served through a CDN and sized for phones. Recovery is tested every year, and the result is written down.

  2. Make the calendar the record

    Exhibitions, performances, classes, and closures are entered once, as events with dates, and appear on the homepage, the calendar, and an iCalendar feed people can subscribe to. When an exhibition closes, its page becomes an archive entry instead of a broken link.

  3. Make accessibility a monthly number

    Templates are built and tested to WCAG 2.1 AA once. After that every page is scanned daily, and findings are listed by page and owner. An image without a description cannot be published, which matters most on a site whose pages are mostly images.

What the monthly fee covers

Routine tasks of 30 minutes or less, handled one at a time. Standard acknowledgment: one business day. Priority acknowledgment: four business hours. These are response targets; completion depends on the work.

Business hours only, with no after-hours or on-call coverage. Hosting and licenses are paid separately. Redesigns, integrations, custom development, and larger remediation work receive a separate fixed quote.

Read management scope and terms

Before you engage

What arts organizations ask first.

Can the website work with our ticketing and membership systems?

Yes. Tessitura, Spektrix, Eventbrite, Blackbaud, and similar systems keep selling tickets and managing members. The website links to them consistently, styles what can be embedded, and never stores card details. Where a system publishes a feed, event listings are read from it instead of retyped.

Do we have to leave our current platform?

No. If the site already runs on WordPress, LFW takes over maintenance where it is or moves it to managed hosting. Leaving a proprietary museum or library platform is a rebuild, with its own scope, schedule, and fixed quote.

How do you handle image credits and rights?

Every image carries a credit and a description, entered at upload and shown wherever the image appears. Images that may not be reused are kept out of the public media library and out of search engines.

What about a collections database or a library catalog?

Those stay in their systems. The website links to the record in the catalog or collections database rather than copying it, so the catalog remains the record and the site stays small enough to keep accurate.

For public museums and libraries

The accessibility rule covers public cultural institutions.

Relevant experience

Experience with busy calendars and many editors.

At Stand Together, Leland worked on the in-house team responsible for more than 100 sites running WordPress, including event-driven campaign sites with shared templates and editors who were not developers. He also administered Arlington County Government’s network of more than 40 public sites. Both roles preceded LFW.

These are roles Leland held before founding LFW. The organizations named here are former employers, not LFW client references.

Read Leland’s professional history
The work leaves a record. Enlarge screenshot
A real view of the LFW demo service report

Enlarge to view the full screenshot.

A real view of the LFW demo service report Read the sample service report

Bring the page that changes most often.

Show us the calendar, the exhibition template, the hours page, or the RFP you are writing. We can say which parts belong in ongoing management and which need a defined project.

    Powered by LFW Search
    Prefer to write?

    Tell us what needs to work better.

    Slow, fragile, hard to edit, missing a workflow. Say it plainly, and you'll get a straight answer, not a ticket number.