Use when a devopsdays event that is already listed on the site has to be cancelled or postponed, and its pages need to stop advertising dates, registration, and sponsorship.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
The goal is that the event stops appearing as upcoming, its dead pages redirect instead of 404ing, and anyone who lands on it sees why.
The site filters events with cancel: "true" out of the upcoming, all-events and TBD listings.
The value is a case-sensitive string in quotes.
There is no script for this. Work through it by hand.
Keep three: welcome.md, contact.md, conduct.md (plus translated conduct pages if the event
has them). Delete the rest from content/events/<YYYY>-<city-slug>/:
cd content/events/2026-ponyville
rm -f location.md propose.md registration.md sponsor.md program.md speakers.md talks.md
rm -rf program speakers
Anyone with a bookmark should land on the welcome page, not a 404. Add aliases to welcome.md's
frontmatter, one per page you deleted:
+++
Title = "devopsdays Ponyville 2026"
Type = "welcome"
Description = "devopsdays Ponyville 2026 has been cancelled."
aliases = [
"/events/2026-ponyville/",
"/events/2026-ponyville/location/",
"/events/2026-ponyville/propose/",
"/events/2026-ponyville/registration/",
"/events/2026-ponyville/sponsor/",
"/events/2026-ponyville/program/",
"/events/2026-ponyville/speakers/"
]
+++
Then replace the body with the cancellation notice. Say what happened, and whether people should expect the event to return, and how to reach the team. This is the page everyone will see.
In data/events/<YYYY>/<city-slug>/main.yml:
cancel: "true"
startdate:
enddate:
cfp_date_start:
cfp_date_end:
cfp_date_announce:
registration_date_start:
registration_date_end:
location:
location_address:
sponsors_accepted: "no"
description: "devopsdays Ponyville 2026 has been cancelled."
nav_elements:
- name: contact
- name: conduct
Blank the dates rather than deleting the keys. Trim nav_elements to the pages that still exist —
leaving a nav entry for a deleted page produces a dead link.
Leave the sponsors: list alone. Sponsors who supported the event stay credited.
If location.md used {{< event_map >}} and you blank coordinates, the build breaks. The
shortcode reads coordinates before checking whether there is an address, so a blank value is a
hard failure, not a graceful skip.
Deleting location.md in step 1 avoids this entirely. If the event keeps a location page for some
reason, remove the {{< event_map >}} shortcode from it.
Leave the city's line in static/_redirects pointing at this event. When the city runs again,
new-event bumps the year. Pointing /ponyville/ at a cancelled event is better than pointing it
at nothing.
cancel: "true" is quoted, lowercase true, and spelled cancel not cancelled/events/ after a rebuildnav_elements entry has a page{{< event_map >}} survives with blank coordinates/events/<YYYY>-<city-slug>/ and try one of the old URLsFollow .claude/skills/submit-changes/SKILL.md.
PR title: [PONY-2026] Cancel Ponyville 2026.
This is a visible change affecting people who bought tickets or submitted talks. Make sure the organizers have actually announced it before the PR merges.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when adding, removing, or updating a local organizer on a devopsdays event team - covers the team_members entry, the photo, and the mandatory email to info@devopsdays.org that gates the merge.
The English summary is being prepared. Showing the original description.
Use when a devopsdays event has confirmed a speaker and their talk, workshop, ignite, or keynote needs to appear on the event site - covers the speaker bio page, the talk page, the headshot, and multi-speaker talks.
The English summary is being prepared. Showing the original description.
Use when a devopsdays event has sold or confirmed a sponsorship and the sponsor needs to appear on the event's site - covers both sponsors already in the shared directory and brand-new ones needing a logo and data file.
The English summary is being prepared. Showing the original description.
Use when a devopsdays event has finished and the slides or video recordings need to be attached to the talk pages, or when a speaker sends a link to their deck afterwards.
The English summary is being prepared. Showing the original description.
Use when building or editing a devopsdays event's schedule - adding talks, ignites, open spaces, breaks, and evening events to the program, or moving time slots around.
The English summary is being prepared. Showing the original description.
Use when a sponsor has rebranded or sent an updated logo and it must change on current and future events without altering how they appeared at past devopsdays events.
The English summary is being prepared. Showing the original description.