Contact

Send a lead, listing, correction, or question.

Dripping Springs Buzz works best when local information arrives early, clearly, and with enough context to verify. Send public events, business updates, civic notes, school-adjacent reminders, venue weekends, corrections, photos, and story leads that would help residents understand what is happening around town.

The most useful submissions are not necessarily long. They are specific. A date without a time creates another search. A business announcement without an address leaves readers guessing. A meeting note without an agenda link is hard to verify. A photo without a credit cannot be used responsibly. The more complete the first note is, the faster it can become a useful listing or story.

Events and calendar items

Events should be public or broadly community-relevant. That includes city meetings, nonprofit fundraisers, school programs open to the community, library activities, markets, live music, venue open houses, family events, volunteer days, local sports notes, seasonal festivals, and public workshops. Private parties, vague promotions, and items without verifiable details are less likely to be published.

Send event details as early as possible. Last-minute events may still be useful, but the Buzz is meant to help residents plan the week, not simply document what already happened. If an event is weather-sensitive, include the rain plan or cancellation source. If a ticket or RSVP is required, include the exact link readers should use.

• Event name exactly as the organizer wants it listed.
• Date, start time, end time if known, and whether the schedule is flexible.
• Venue name, street address, parking notes, and accessibility details if available.
• Cost, ticket link, RSVP requirement, age range, pet policy, and food or drink notes.
• Organizer name, public source link, and a contact person for verification.

Business and directory updates

The directory is not meant to become a thin list of names. Send the details that help a resident decide whether a place fits the plan: hours, service area, reservation habits, price expectations, parking, family friendliness, outdoor seating, accessibility, appointment requirements, emergency availability, and any local detail that does not show up in a generic search result.

Openings, closings, relocations, expanded hours, new patios, seasonal menus, vendor markets, tasting-room changes, and service-area updates are all useful when they are verifiable. If the update affects a weekend crowd, nearby traffic, a neighborhood, or a regular community habit, say so. That context is often more useful than a polished announcement.

• Business name, category, address or service area, and public website or social link.
• What changed, when it changed, and whether the update is permanent, seasonal, or temporary.
• Resident-useful details: parking, hours, booking, family fit, outdoor space, cost, or appointment needs.
• Photos with photographer credit and confirmation that the image may be published.

Civic, school, and public-source tips

Civic tips need a source. That can be an agenda, packet, public notice, city page, school board document, utility notice, road update, or official calendar entry. A useful civic submission explains what the item is, why residents may care, and what question a reader should ask before the meeting or deadline passes.

The Buzz will not publish unsupported accusations or turn a complicated public issue into a one-sided post. It will, however, make room for plain-language explainers about growth, water, roads, parks, development proposals, public safety, school calendars, and the civic process. Send the source first, then add your local context separately.

• Link to the official agenda, public notice, department page, or source document.
• Meeting date, board or department name, and the deadline for public action if there is one.
• The plain-language reason a resident should care.
• Names and titles of people or agencies involved, spelled exactly as the source uses them.

Corrections, photo credits, and attribution

Corrections should be direct: send the page URL, the sentence or listing that is wrong, and the source that shows the correct information. If the issue is a nuance rather than a factual error, explain the missing context and include a source when possible. The goal is to improve the public record, not make corrections hard to request.

Photos need permission and credit. If you send an image, include the photographer name, business or organization if relevant, caption details, and whether the image can be cropped. Avoid sending photos of minors unless the event organizer has already handled permission or the photo is an official public image meant for publication.

Where to send it

Email is the cleanest starting point for now. Put the category in the subject line when possible: event, business update, correction, civic tip, photo, sponsorship, or story lead. If a note needs a reply by a specific date, say that near the top.

The Buzz will keep improving the submission workflow as the site grows. For launch, clarity beats formality. Send the details, include the source, and make it easy for a local reader to act on the information.

For now, assume every submission is reviewed by a person before it becomes public. That means the site may not publish every announcement exactly as submitted, and it may ask for a source before using a claim. The tradeoff is intentional. A local site earns trust by slowing down just enough to verify dates, names, links, and practical details.

If the note is sensitive, say what can be published and what is background. If the issue involves a business, agency, venue, school, or public body, include the best contact for a response. Good local coverage is not built from anonymous fragments alone; it needs documents, names, and a fair chance to check the facts.

When in doubt, send the note anyway and label what is confirmed, what is uncertain, and what needs a follow-up.