How we research
C. V. Wooster writes this guide at Taciturn Studios. A festival enters the file when its own website, or the library, city, or humanities council that produces it, describes the event. The calendar, the deadline list, and the state notes all read that file.
What gets stored
For each festival we try to record the name, the host, the city and venue, a typical month or an announced date, whether admission is free or paid, whether authors can apply, whether exhibitors or vendors can apply, a programming note, the official URL, and the day we opened the page. On November 21, 2026 the file held 35 festivals. The sources page lists every URL.
A field is filled only with language the page supports. “Free and open to the public” becomes free admission. “Buy tickets early,” with no free public day, becomes ticketed. A weekend that is free at the gate and paid for a headliner is marked as both, and the note says which part is which. A handbook that mentions payment without printing the dollar amount does not become a fee on this site.
What stays blank
If the organizer does not state a date, we do not copy one from a previous year. If the homepage thanks people for attending and never names the days, the record says the festival was held and leaves the calendar dates off. Six Bridges Book Festival in Little Rock is that case. If a page’s title and its body disagree, as the Los Angeles Times Festival of Books page does about April 2026, both versions are quoted and neither is silently corrected.
Attendance figures are repeated only when the festival site displays them, and they are attributed to that display. They are not forecasts. A survey, a press kit, or a sponsor’s round number is not upgraded into a fact the organizer did not publish.
Pages we will not build
A state with no festival we could describe does not get a long page of library boilerplate. Those URLs stay up so an old link explains itself, they send a noindex tag, and they are absent from the sitemap. The state list names them in one sentence. Repeating the same questions on every state, with the nouns swapped, is the pattern this revision is built to leave behind.
How the tools stay honest
The calendar filters the file. It cannot know about a festival we did not open. The application windows are the author and exhibitor notes, grouped by whether the page said open, closed, invitation, or email. The checklist prints those notes and the fraud warnings. None of the three calls a festival, sells a booth, or stores the state you pick on our server.
Corrections
Organizers change dates after we look. If you have the new URL, send it. We open that page before we change a line, and we log the change on updates. Advertising and the Amazon links elsewhere on the site do not choose which festivals appear. A featured listing, when the site offers one, is labeled paid and is not inserted into the verified file.
A fact is stored only when the festival's own site, or the library or humanities council that produces it, states it. The Library of Congress pages are the source for the National Book Festival. Dates, prices, and deadlines that those pages do not state are left blank.