/**
 * TS Planning Center — event list styles.
 *
 * Deliberately minimal and low-specificity so AdoreChurch's own typography and
 * colours win wherever they apply. Uses currentColor and inherited fonts rather
 * than hard-coded values, so this list looks native on any page it lands on.
 */

.ts-pc-events {
	list-style: none;
	margin: 0 0 1.5em;
	padding: 0;
}

.ts-pc-event {
	padding: 1em 0;
	border-bottom: 1px solid rgba(127, 127, 127, 0.25);
}

.ts-pc-event:last-child {
	border-bottom: 0;
}

.ts-pc-event__date {
	display: block;
	font-size: 0.85em;
	letter-spacing: 0.04em;
	text-transform: uppercase;
	opacity: 0.75;
}

.ts-pc-event__title {
	margin: 0.2em 0 0.3em;
	font-size: 1.15em;
	line-height: 1.3;
}

.ts-pc-event__title a {
	text-decoration: none;
}

.ts-pc-event__title a:hover,
.ts-pc-event__title a:focus {
	text-decoration: underline;
}

.ts-pc-event__location,
.ts-pc-event__desc {
	margin: 0 0 0.3em;
	font-size: 0.95em;
}

.ts-pc-event__location {
	opacity: 0.8;
}

.ts-pc-event__location:before {
	content: "\1F4CD";
	margin-right: 0.4em;
	/* Decorative; screen readers get the text that follows. */
	speak: never;
}

/*
 * ---------------------------------------------------------------------------
 * Source colours
 *
 * Taken from the site's existing palette rather than invented: #007f7b is the
 * brand teal used throughout, #46ca9b its brighter companion, #3bafda the
 * blue accent. Purple is the one addition, for Planning Center.
 * ---------------------------------------------------------------------------
 */
:root {
	--ts-pc-site: #007f7b;
	--ts-pc-site-bright: #46ca9b;
	--ts-pc-google: #3bafda;
	--ts-pc-google-bright: #8ed3ee;
	--ts-pc-pc: #7b5ea7;
	--ts-pc-pc-bright: #9b7cc7;
}

/*
 * Calendar entries.
 *
 * Neutral at rest: a light grey wash and a quiet border, so a busy month reads
 * as one calm surface rather than a colour chart. Colour arrives on hover, as
 * a gradient outline running between the colours of the calendars the event
 * belongs to. The logo marks keep their own colours throughout, so where an
 * event comes from stays legible without tinting every cell.
 *
 * The grey is a literal rgba rather than a token: a mid grey at low opacity
 * sits correctly on both the light and dark versions of the site, which a
 * fixed light or dark tone would not.
 */
.fc-event.ts-pc-cal-event,
a.fc-event.ts-pc-cal-event {
	position: relative;
	padding-right: 1.6em;
	/*
	 * Transparent on every side so the box never changes size between states;
	 * which edges show is decided by the ring below. Left and top are coloured
	 * here as the fallback where masks are unsupported.
	 */
	border: 2px solid transparent;
	border-left-color: rgba(128, 128, 128, 0.5);
	border-top-color: rgba(128, 128, 128, 0.5);
	background-color: rgba(128, 128, 128, 0.05);
	color: inherit;
	transition: background-color 0.15s ease;
}

/*
 * Hover: the background just deepens, and the edge takes the source colours.
 *
 * A solid border is the base, so the edge is correct everywhere. Where masks
 * are supported the ring below replaces it with a gradient while keeping the
 * corner radius — which border-image would have squared off.
 */
.fc-event.ts-pc-cal-event:hover,
a.fc-event.ts-pc-cal-event:hover {
	background-color: rgba(128, 128, 128, 0.2);
	border-color: var(--ts-pc-source, #007f7b);
	color: inherit;
}

/*
 * A gradient ring that respects border-radius: paint the gradient over the
 * element, then mask out everything except a 1px band at its edge. Two mask
 * layers, one inset by the padding, excluded from each other, leave the band.
 */
@supports ((-webkit-mask-composite: xor) or (mask-composite: exclude)) {
	.fc-event.ts-pc-cal-event,
	a.fc-event.ts-pc-cal-event {
		border-left-color: transparent;
		border-top-color: transparent;
	}

	/*
	 * At rest only the left and top edges are drawn, which is what makes an
	 * entry running across several days read as one bar rather than a series of
	 * boxes. Hovering closes the same line around the whole entry.
	 *
	 * Padding decides which edges appear: the mask keeps the area outside the
	 * content box, so padding on two sides leaves two bands and padding on all
	 * four leaves a full ring.
	 */
	.fc-event.ts-pc-cal-event::before {
		content: "";
		position: absolute;
		inset: -2px;
		border-radius: inherit;
		padding: 2px 0 0 2px;
		background: linear-gradient(
			135deg,
			var(--ts-pc-source, #007f7b),
			var(--ts-pc-source-2, #46ca9b)
		);
		-webkit-mask:
			linear-gradient(#000 0 0) content-box,
			linear-gradient(#000 0 0);
		mask:
			linear-gradient(#000 0 0) content-box,
			linear-gradient(#000 0 0);
		-webkit-mask-composite: xor;
		mask-composite: exclude;
		opacity: 0.5;
		pointer-events: none;
		transition: opacity 0.15s ease;
	}

	/* Selected and hovered both close the line all the way round. */
	.fc-event.ts-pc-cal-event:hover::before,
	.fc-event.ts-pc-cal-event.is-active::before {
		padding: 2px;
		opacity: 1;
	}

	.fc-event.ts-pc-cal-event.is-active {
		border-color: transparent;
	}
}

/*
 * The entry the preview is currently showing.
 *
 * Its own colour, well diluted and carried mostly by grey, so it reads as
 * selected without competing with the hover state or the today ring.
 */
.fc-event.ts-pc-cal-event.is-active {
	background-color: rgba(128, 128, 128, 0.16);
	background-color: color-mix(in srgb, var(--ts-pc-source, #007f7b) 12%, rgba(128, 128, 128, 0.14));
	/* Fallback where the ring below cannot be drawn. */
	border-color: var(--ts-pc-source, #007f7b);
}

.fc-event.ts-pc-cal-event .fc-title,
.fc-event.ts-pc-cal-event .fc-time {
	color: inherit;
}

/* Which two colours the hover outline runs between. */
.fc-event.ts-pc-cal-event--site {
	--ts-pc-source: var(--ts-pc-site);
	--ts-pc-source-2: var(--ts-pc-site-bright);
}

.fc-event.ts-pc-cal-event--google {
	--ts-pc-source: var(--ts-pc-google);
	--ts-pc-source-2: var(--ts-pc-google-bright);
}

.fc-event.ts-pc-cal-event--pc {
	--ts-pc-source: var(--ts-pc-pc);
	--ts-pc-source-2: var(--ts-pc-pc-bright);
}

/*
 * An event in both Google and Planning Center but nowhere on the site belongs
 * to neither, so its outline runs between the two calendars' own colours.
 */
.fc-event.ts-pc-cal-event--combo {
	--ts-pc-source: var(--ts-pc-google);
	--ts-pc-source-2: var(--ts-pc-pc);
}

/* Logo marks stay in their own calendar's colour, hovered or not. */
.ts-pc-badge--site { --ts-pc-mark: var(--ts-pc-site); }
.ts-pc-badge--google { --ts-pc-mark: var(--ts-pc-google); }
.ts-pc-badge--pc { --ts-pc-mark: var(--ts-pc-pc); }

/*
 * Corner marks, one per other calendar the event lives in.
 * Faint until the event is hovered, so a busy month stays calm.
 */
.ts-pc-badge {
	position: absolute;
	top: 2px;
	right: 2px;
	display: inline-flex;
	align-items: center;
	justify-content: center;
	width: 16px;
	height: 16px;
	border: 0;
	border-radius: 3px;
	background: transparent;
	color: var(--ts-pc-mark, currentColor);
	opacity: 0.5;
	cursor: pointer;
	transition: opacity 0.15s ease, background-color 0.15s ease, border-color 0.15s ease;
}

.fc-event.ts-pc-cal-event:hover .ts-pc-badge { opacity: 1; }

.ts-pc-badge:hover,
.ts-pc-badge:focus {
	opacity: 1;
	background-color: var(--ts-pc-mark, currentColor);
	color: #fff;
	outline: none;
}

.ts-pc-badge svg {
	/* Real logo artwork: filled paths taking the source colour, not line art. */
	fill: currentColor;
	stroke: none;
}

.ts-pc-badge--google svg {
	width: 13px;
	height: 13px;
}

.ts-pc-badge--pc svg {
	width: 16px;
	height: 16px;
}

/* Room for a second mark when an event lives in two other calendars. */
.fc-event.ts-pc-cal-event--merged {
	padding-right: 2.8em;
}

.ts-pc-badge + .ts-pc-badge {
	right: 21px;
}

/*
 * An entry spanning several days.
 *
 * The first line is split into one cell per day, each repeating the time and
 * carrying that day's calendar links, so a link sits under the column it refers
 * to instead of piling into a corner. The title keeps the second line to
 * itself, matching every other entry in the grid.
 */
.fc-event.ts-pc-cal-event--spanning {
	padding-right: 0;
	/* The strip is pulled out to the column edges, so it must not be clipped. */
	overflow: visible;
}

/*
 * The library clips this box, and the strip lives inside it.
 *
 * The entry is inset from its columns by its margin and its border, so the
 * last day's cell — placed at that column's own edge — reaches past the box
 * and takes its mark with it. Every earlier day sits well inside, which is
 * why only the final day of a run lost its link.
 */
.fc-event.ts-pc-cal-event--spanning > .fc-content {
	overflow: visible;
}

/* The theme's single time is replaced by one per day in the strip. */
.fc-event.ts-pc-cal-event--spanning .fc-time {
	display: none;
}

/*
 * The cells are positioned absolutely from their columns' own rectangles, so
 * the strip is only a positioning context and a reserved line of height.
 */
.ts-pc-daystrip {
	position: relative;
	display: block;
	height: 18px;
}

/*
 * Widths are set in script, from the real column geometry — equal shares of the
 * entry do not line up, because the entry is inset from the column edges. The
 * flex basis here is only the starting point before that measurement.
 */
.ts-pc-daystrip__cell {
	/*
	 * The width set in script is the column's full width, so the padding has to
	 * sit inside it. Without this the cells run wide by their padding and the
	 * error accumulates across the span, pushing each mark further off its day.
	 */
	box-sizing: border-box;
	display: flex;
	align-items: center;
	justify-content: space-between;
	gap: 4px;
	height: 18px;
	padding: 0 4px 0 3px;
	overflow: hidden;
}

/*
 * Marks sit at the right of their own cell, Google to the left of Planning
 * Center. The cell is already the width of its column, so its right edge is
 * the only measurement involved — nothing here is placed by arithmetic.
 */
.ts-pc-daystrip__marks {
	display: flex;
	align-items: center;
	flex: 0 0 auto;
	gap: 3px;
	height: 18px;
}

.ts-pc-daystrip__time {
	/* Yields to the marks, which cannot shrink, and ellipses instead. */
	flex: 0 1 auto;
	min-width: 0;
	font-weight: 700;
	white-space: nowrap;
	overflow: hidden;
	text-overflow: ellipsis;
}

/* Inside the strip the badges sit in flow rather than pinned to a corner. */
.ts-pc-daystrip .ts-pc-badge {
	position: static;
	flex: 0 0 auto;
}

/*
 * "Also on" links, and the banner on a non-website event.
 *
 * Styled like the calendar entries they refer to: a faint wash of the source
 * colour, a full-strength border, and the same lift on hover. Text keeps the
 * theme's colour; only the border and mark carry the source's identity, which
 * is what keeps them readable in dark mode.
 */
/*
 * Where else the event is listed.
 *
 * No rule above it and no heading: an event kept on this site and an event
 * read out of Church Center are both simply listed in more than one place,
 * and labelling one set of links and not the other made a distinction out of
 * nothing.
 */
.ts-pc-preview__also {
	display: flex;
	align-items: center;
	gap: 0.3em;
	margin-top: 0.9em;
}

.ts-pc-preview__also-track {
	flex: 1 1 auto;
	min-width: 0;
}

/*
 * The arrows belong to the narrow layout, where the links run across instead
 * of down. On a wide screen the list is a column and there is nothing to
 * scroll, so they never appear.
 */
.ts-pc-preview__also-nav {
	display: none;
	flex: 0 0 auto;
	width: 22px;
	height: 30px;
	padding: 0;
	border: 1px solid rgba(128, 128, 128, 0.3);
	border-radius: 3px;
	background: rgba(128, 128, 128, 0.05);
	color: inherit;
	font-size: 1.1em;
	line-height: 1;
	cursor: pointer;
}

.ts-pc-preview__also-nav[disabled] {
	opacity: 0.3;
	cursor: default;
}

.ts-pc-preview__chip,
.ts-pc-preview__banner {
	--ts-pc-source: var(--ts-pc-pc);
	--ts-pc-source-2: var(--ts-pc-pc-bright);
	display: flex;
	align-items: center;
	gap: 0.65em;
	margin-bottom: 0.45em;
	padding: 0.6em 0.75em;
	border: 1px solid rgba(128, 128, 128, 0.3);
	border-radius: 3px;
	background-color: rgba(128, 128, 128, 0.05);
	color: inherit;
	font-size: 0.9em;
	text-decoration: none;
	transition: background-color 0.15s ease;
}

.ts-pc-preview__chip--google,
.ts-pc-preview__banner--google {
	--ts-pc-source: var(--ts-pc-google);
	--ts-pc-source-2: var(--ts-pc-google-bright);
}

.ts-pc-preview__chip--site,
.ts-pc-preview__banner--site {
	--ts-pc-source: var(--ts-pc-site);
	--ts-pc-source-2: var(--ts-pc-site-bright);
}

/* Same treatment on the preview chips. */
.ts-pc-preview__chip,
.ts-pc-preview__banner {
	position: relative;
}

.ts-pc-preview__chip:hover,
.ts-pc-preview__chip:focus,
.ts-pc-preview:hover .ts-pc-preview__banner {
	background-color: rgba(128, 128, 128, 0.2);
	border-color: var(--ts-pc-source);
	color: inherit;
}

@supports ((-webkit-mask-composite: xor) or (mask-composite: exclude)) {
	.ts-pc-preview__chip:hover,
	.ts-pc-preview__chip:focus,
	.ts-pc-preview:hover .ts-pc-preview__banner {
		border-color: transparent;
	}

	.ts-pc-preview__chip:hover::before,
	.ts-pc-preview__chip:focus::before,
	.ts-pc-preview:hover .ts-pc-preview__banner::before {
		content: "";
		position: absolute;
		inset: -2px;
		border-radius: inherit;
		padding: 2px;
		background: linear-gradient(135deg, var(--ts-pc-source), var(--ts-pc-source-2));
		-webkit-mask:
			linear-gradient(#000 0 0) content-box,
			linear-gradient(#000 0 0);
		mask:
			linear-gradient(#000 0 0) content-box,
			linear-gradient(#000 0 0);
		-webkit-mask-composite: xor;
		mask-composite: exclude;
		pointer-events: none;
	}
}

/*
 * Two lines rather than two columns: the mark sits with the link it belongs
 * to, and the detail below runs the full width of the card. Indenting that
 * line past the mark left a narrow column of text in an already narrow panel.
 */
.ts-pc-preview__chip {
	display: block;
}

.ts-pc-preview__chip-line {
	display: flex;
	align-items: center;
	/* Word spacing between the words; the mark keeps its own distance below. */
	gap: 0.3em;
}

.ts-pc-preview__chip-line .ts-pc-preview__chip-mark {
	margin-right: 0.35em;
}

.ts-pc-preview__chip em {
	display: block;
	margin-top: 0.3em;
	font-size: 0.85em;
	font-style: normal;
	opacity: 0.75;
}

/*
 * When that calendar has it, and what it calls it where that differs: a line
 * each, and the same weight. Setting the time in a smaller type than the name
 * made it the footnote of a footnote, and with the name gone it is all the
 * line there is.
 */
.ts-pc-preview__chip-when {
	display: block;
	overflow: hidden;
	white-space: nowrap;
	text-overflow: ellipsis;
}

.ts-pc-preview__chip-mark,
.ts-pc-preview__banner-mark {
	display: inline-flex;
	align-items: center;
	justify-content: center;
	flex: 0 0 auto;
	width: 18px;
	height: 18px;
	border-radius: 3px;
	color: var(--ts-pc-source);
	transition: background-color 0.15s ease;
}

.ts-pc-preview__chip-mark:hover,
.ts-pc-preview__banner-mark:hover {
	background-color: var(--ts-pc-source);
	color: #fff;
}

.ts-pc-preview__chip-mark svg,
.ts-pc-preview__banner-mark svg {
	fill: currentColor;
	stroke: none;
}

.ts-pc-preview__chip--google .ts-pc-preview__chip-mark svg,
.ts-pc-preview__banner--google .ts-pc-preview__banner-mark svg {
	width: 15px;
	height: 15px;
}

/* Planning Center is the default size here; Google is stepped down above. */
.ts-pc-preview__chip-mark svg,
.ts-pc-preview__banner-mark svg {
	width: 18px;
	height: 18px;
}

/* Planning Center event shown in the theme's preview column. */
.ts-pc-preview {
	cursor: pointer;
}

.ts-pc-preview__image {
	display: block;
	margin-bottom: 1em;
}

.ts-pc-preview__image img {
	display: block;
	width: 100%;
	height: auto;
}

.ts-pc-preview__title {
	margin: 0 0 0.4em;
	font-size: 1.25em;
	line-height: 1.3;
}

.ts-pc-preview__date {
	margin: 0 0 0.4em;
	font-weight: 600;
}

.ts-pc-preview__location {
	margin: 0 0 0.8em;
	opacity: 0.8;
}

.ts-pc-preview__blurb {
	margin: 0 0 1em;
}

/* Admin-only notice when the Planning Center feed is unavailable. */
.ts-pc-notice {
	padding: 0.6em 0.9em;
	margin-bottom: 1em;
	border-left: 3px solid #d98500;
	background: rgba(217, 133, 0, 0.08);
	font-size: 0.9em;
}

.ts-pc-empty {
	opacity: 0.7;
	font-style: italic;
}

/*
 * ---------------------------------------------------------------------------
 * Calendar chrome
 * ---------------------------------------------------------------------------
 */

/*
 * The theme gives the toolbar a heavy striped panel that does not invert with
 * the site's dark mode, so it stays pale against dark pages. A translucent
 * wash sits correctly either way.
 *
 * Laid out as one row rather than the library's floated thirds, which spread
 * the pieces across the full width and dropped the buttons to a second line
 * once the title held fields instead of plain text.
 */
.fc-toolbar,
.fc .fc-toolbar {
	display: flex;
	align-items: center;
	flex-wrap: wrap;
	gap: 0.6em;
	background: rgba(128, 128, 128, 0.08);
	background-image: none;
	border-radius: 3px;
	padding: 0.3em 0.6em;
	margin-bottom: 0.6em;
}

/*
 * The library appends the sections left, right, centre — the middle one last.
 * Reading order has to be restored explicitly, or the empty middle section
 * lands past the buttons and takes the slack meant to push them to the end.
 */
.fc-toolbar .fc-left {
	order: 1;
}

.fc-toolbar .fc-center {
	order: 2;
	/* The empty middle takes the slack, so the buttons sit at the far end. */
	flex: 1 1 auto;
}

.fc-toolbar .fc-right {
	order: 3;
}

.fc-toolbar .fc-left,
.fc-toolbar .fc-center,
.fc-toolbar .fc-right {
	float: none;
	display: flex;
	align-items: center;
	gap: 0.4em;
	margin: 0;
	padding: 0;
}

.fc-toolbar .fc-clear {
	display: none;
}

.fc-toolbar h2 {
	display: inline-flex;
	align-items: center;
	gap: 0.35em;
	font-size: 1.35em;
	/* Sits level with the buttons rather than riding above them. */
	line-height: 1;
	margin: 0;
	padding: 0;
}

/*
 * Scoped past the theme's own button styling, which sets a height and padding
 * site-wide and was what made this bar so tall.
 */
.fc .fc-toolbar .fc-button,
.post-content .fc .fc-toolbar .fc-button,
.fc-toolbar .fc-button {
	height: auto;
	min-height: 0;
	padding: 0.3em 0.7em;
	line-height: 1.35;
	font-size: 0.9em;
	text-transform: none;
	letter-spacing: normal;
}

.fc-toolbar .fc-button-group {
	display: inline-flex;
	align-items: center;
}

/* The bar is only as tall as what it holds. */
.fc .fc-toolbar,
.fc-toolbar {
	min-height: 0;
}

/*
 * Month, year and timezone read as text and behave as fields.
 *
 * A select in the middle of a heading looks like a form. These show the value
 * plainly, underline on hover to say they can be used, and become editable on
 * click — typed into or chosen from, whichever suits.
 */
.ts-pc-pick {
	position: relative;
	display: inline-block;
}

.ts-pc-pick__field {
	width: auto;
	min-width: 2ch;
	padding: 0 0 2px;
	border: 0;
	border-bottom: 2px solid transparent;
	border-radius: 0;
	background: none;
	box-shadow: none;
	color: inherit;
	font: inherit;
	font-weight: 700;
	font-size: 1.1em;
	line-height: inherit;
	cursor: pointer;
}

.ts-pc-pick__field:hover {
	border-bottom-color: rgba(128, 128, 128, 0.6);
}

.ts-pc-pick__field:focus {
	border-bottom-color: currentColor;
	outline: none;
	cursor: text;
}

.ts-pc-pick + .ts-pc-pick {
	margin-left: 0.4em;
}

.ts-pc-pick__list {
	position: absolute;
	top: 100%;
	left: 0;
	z-index: 20;
	min-width: 100%;
	max-height: 16em;
	margin: 2px 0 0;
	padding: 0.25em 0;
	overflow-y: auto;
	list-style: none;
	border: 1px solid rgba(128, 128, 128, 0.35);
	border-radius: 3px;
	background: #fff;
	box-shadow: 0 4px 14px rgba(0, 0, 0, 0.18);
}

/* The site has a dark mode, and a white list would glare inside it. */
@media (prefers-color-scheme: dark) {
	.ts-pc-pick__list {
		background: #23282d;
	}
}

.ts-pc-pick__option {
	margin: 0;
	padding: 0.3em 0.9em;
	font-size: 0.85rem;
	font-weight: 400;
	white-space: nowrap;
	cursor: pointer;
}

.ts-pc-pick__option:hover,
.ts-pc-pick__option.is-active {
	background: rgba(128, 128, 128, 0.2);
}

/* The timezone sits beside the arrows, quieter than the title. */
.ts-pc-pick--zone {
	margin-left: 0.6em;
}

.ts-pc-pick--zone .ts-pc-pick__field {
	font-size: 0.75rem;
	letter-spacing: 0.04em;
	text-transform: uppercase;
	opacity: 0.75;
}

.ts-pc-pick--zone .ts-pc-pick__field:hover,
.ts-pc-pick--zone .ts-pc-pick__field:focus {
	opacity: 1;
}

/*
 * Day numbers sit clear of the cell edge, so the today ring cannot run
 * through them.
 *
 * One value for both the open rows and the folded ones: they are different
 * elements in different tables, and tuning them separately is what let them
 * drift apart. Marked important because the library's own stylesheet is
 * enqueued after this one and sets its own padding here.
 */
:root {
	--ts-pc-date-inset: 8px;
}

.fc .fc-day-number,
.fc-basic-view td.fc-day-number,
.fc-basic-view .fc-day-number,
.post-content .fc-row .fc-content-skeleton td.fc-day-number {
	padding-right: var(--ts-pc-date-inset) !important;
}

/* The folded weeks keep the same distance from the edge. */
.ts-pc-strip .ts-pc-strip__date {
	padding-right: var(--ts-pc-date-inset) !important;
}

/*
 * Days already gone.
 *
 * Dimmed rather than hidden, and restored on hover, so a past event is still
 * readable when looked at directly but stops competing with what is ahead.
 */
.fc-day-number.fc-past,
.fc-day-top.fc-past {
	opacity: 0.45;
}

.fc-event.ts-pc-past {
	opacity: 0.4;
	transition: opacity 0.15s ease;
}

.fc-event.ts-pc-past:hover {
	opacity: 1;
}

/*
 * Today.
 *
 * A ring rather than a fill: the wash read as another event's background, and
 * a border survives the site's dark mode where a pale yellow does not.
 *
 * Drawn on a layer of its own rather than as an inset shadow, so it can have
 * rounded corners — a shadow inside a collapsed table cell cannot.
 */
.fc-day.fc-today,
.fc-bg .fc-today {
	/*
	 * The library's own pale yellow is opaque and loses the dark page beneath
	 * it, so the tint is carried by the ring's own colour instead. Important
	 * because that stylesheet is enqueued after this one.
	 */
	background: rgba(226, 178, 26, 0.07) !important;
	box-shadow: none;
	position: relative;
}

.fc-bg .fc-today:after,
.fc-day.fc-today:after {
	content: "";
	position: absolute;
	inset: 0;
	border: 2px solid rgba(226, 178, 26, 0.9);
	border-radius: 3px;
	box-shadow: 0 0 8px rgba(226, 178, 26, 0.25);
	pointer-events: none;
}

/*
 * Today, answering the button.
 *
 * The ring spreads and fades once, slowly. Pressing Today while this month is
 * already open changes nothing on the page, and a button that appears to do
 * nothing reads as broken.
 */
@keyframes ts-pc-today-pulse {
	0% {
		box-shadow: 0 0 8px rgba(226, 178, 26, 0.25), 0 0 0 0 rgba(226, 178, 26, 0.28);
	}

	100% {
		box-shadow: 0 0 8px rgba(226, 178, 26, 0.25), 0 0 0 14px rgba(226, 178, 26, 0);
	}
}

.fc-bg .fc-today.ts-pc-pulse:after,
.fc-day.fc-today.ts-pc-pulse:after,
.ts-pc-strip .ts-pc-strip__day.is-today.ts-pc-pulse {
	animation: ts-pc-today-pulse 1.3s ease-out 1;
}

@media (prefers-reduced-motion: reduce) {
	.fc-bg .fc-today.ts-pc-pulse:after,
	.fc-day.fc-today.ts-pc-pulse:after,
	.ts-pc-strip .ts-pc-strip__day.is-today.ts-pc-pulse {
		animation: none;
	}
}

/*
 * Finished weeks fold away.
 *
 * The row is hidden outright and this strip stands in its place, at a height
 * set here. Nothing tries to resize the library's row.
 *
 * The month view divides the available height among its rows and expands any
 * that falls below the average, so a row cannot be shortened by emptying it,
 * and a row sized while folded is too short once opened. Both were the same
 * fight with the same arithmetic. A hidden row has no height to argue over,
 * and the library divides the space again afterwards.
 */
.ts-pc-strip {
	position: relative;
	border-bottom: 1px solid rgba(128, 128, 128, 0.18);
}

/*
 * Days are placed against their own columns' rectangles. A table of equal
 * shares cannot match a grid that gives each column an explicit width — any
 * shortfall lands on the last cell, which is why only Saturday lined up.
 */
.ts-pc-strip__inner {
	position: relative;
	height: 1.9em;
}

/*
 * Scoped through the container to outrank the theme's own button styling,
 * which was adding side padding and holding the date well clear of the column
 * edge — the button spans its column exactly, so any inset here is padding.
 */
.ts-pc-strip .ts-pc-strip__day {
	position: absolute;
	top: 0;
	bottom: 0;
	min-width: 0;
	min-height: 0;
	font-family: inherit;
	letter-spacing: normal;
	text-transform: none;
	box-shadow: none;
	display: flex;
	/* Shared baseline, so the count and the date sit level with each other. */
	align-items: baseline;
	justify-content: space-between;
	gap: 0.4em;
	padding: 3px 0 0;
	border: 0;
	border-radius: 2px;
	background: none;
	color: inherit;
	line-height: 1.3;
	text-align: left;
	cursor: pointer;
	transition: background-color 0.15s ease;
}

.ts-pc-strip .ts-pc-strip__day:hover,
.ts-pc-strip .ts-pc-strip__day:focus {
	background: rgba(128, 128, 128, 0.14);
	outline: none;
}

/* Today keeps its ring while its week is folded, matching the open rows. */
.ts-pc-strip .ts-pc-strip__day.is-today {
	border: 2px solid rgba(226, 178, 26, 0.9);
	border-radius: 3px;
	box-shadow: 0 0 8px rgba(226, 178, 26, 0.25);
	/* Keeps the text where it sits on any other day despite the border. */
	padding: 1px 0 0 3px;
}

/*
 * The count reads as an entry's time does — same weight, same corner of the
 * cell — so the folded week matches the rows around it.
 */
/*
 * The countdown, in the panel and in this plugin's own preview: a line of
 * text rather than a panel of boxes, so it sits under a photograph without
 * competing with it.
 */
#events-preview-box .ts-pc-preview__countdown,
.ts-pc-preview__countdown {
	display: block;
	width: 100%;
	margin: 0;
	padding: 0.3em 0.5em;
	background: rgba(128, 128, 128, 0.09);
	font-size: 0.9em;
	line-height: 1.4;
	letter-spacing: 0.02em;
	opacity: 0.7;
	text-align: center;
	white-space: nowrap;
}

.ts-pc-preview__media {
	display: flex;
	flex-direction: column;
}

/* Shown only where the word does not fit. */
.ts-pc-strip__icon {
	display: none;
	width: 0.85em;
	height: 0.85em;
}

.ts-pc-strip__icon svg {
	width: 100%;
	height: 100%;
	fill: none;
	stroke: currentColor;
	stroke-width: 1.6;
	stroke-linecap: round;
}

.ts-pc-strip__count {
	display: inline-flex;
	align-items: baseline;
	gap: 0.3em;
	font-size: 0.8em;
	font-weight: 700;
	opacity: 0.75;
}

/* The date keeps its usual place, dimmed like other past dates. */
.ts-pc-strip__date {
	flex: 0 0 auto;
	/* The distance from the edge is set once, above, for open rows and folded. */
	padding-left: 2px;
	opacity: 0.45;
}

/* Clear of the cell's left border, which the count was sitting against. */
.ts-pc-strip .ts-pc-strip__day {
	padding-left: 5px;
}

/* Opens the week, mirroring the control that closed it. */
.ts-pc-strip__open {
	position: absolute;
	top: 0;
	right: -19px;
	bottom: 0;
	width: 16px;
	display: flex;
	align-items: center;
	justify-content: center;
	padding: 0;
	border: 0;
	background: rgba(128, 128, 128, 0.12);
	color: inherit;
	cursor: pointer;
}

.ts-pc-strip__open:hover,
.ts-pc-strip__open:focus {
	background: rgba(128, 128, 128, 0.24);
	outline: none;
}

.ts-pc-strip__open .ts-pc-week-toggle__caret {
	transform: rotate(180deg);
}

/*
 * The control that folds an open week sits in a gutter beside the grid.
 *
 * The gutter is padding on the calendar itself rather than space outside it,
 * so the control is clear of Saturday's dates without anything needing to be
 * un-clipped — un-clipping the grid is what let rows overlap once before.
 */
.event_calendar.fc,
.fc.calendar {
	padding-right: 20px;
}

.ts-pc-week-toggle {
	position: absolute;
	right: 1px;
	width: 16px;
	z-index: 4;
	display: flex;
	align-items: center;
	justify-content: center;
	padding: 0;
	border: 1px solid rgba(128, 128, 128, 0.3);
	border-right: 0;
	border-radius: 3px 0 0 3px;
	background: rgba(128, 128, 128, 0.1);
	color: inherit;
	cursor: pointer;
	opacity: 0.45;
	transition: opacity 0.15s ease, background-color 0.15s ease;
}

.ts-pc-week-toggle:hover,
.ts-pc-week-toggle:focus {
	opacity: 1;
	background: rgba(128, 128, 128, 0.22);
	outline: none;
}

.ts-pc-week-toggle__caret {
	display: inline-block;
	width: 0;
	height: 0;
	border-left: 4px solid transparent;
	border-right: 4px solid transparent;
	border-bottom: 5px solid currentColor;
	transition: transform 0.15s ease;
}

/*
 * The preview column's list marker.
 *
 * The theme builds the preview as a list, and its own reset does not reach the
 * items in this container, so each one draws a bullet beside the thumbnail.
 * Scoped to the preview so other lists on the site keep their markers.
 */
#events-preview-box ul,
#events-preview-box li,
#events-preview-box .event-item {
	list-style: none;
}

/* The marker is gone, but the indent it sat in is not until this. */
#events-preview-box ul,
#events-preview-box ol {
	margin-left: 0;
	padding-left: 0;
}

#events-preview-box li {
	margin-left: 0;
	padding-left: 0;
}

#events-preview-box li::marker,
#events-preview-box .event-item::marker {
	content: none;
}

/* Our own preview is not a list either. */
.ts-pc-preview,
.ts-pc-preview > * {
	list-style: none;
}

/*
 * Narrow screens.
 *
 * The counts drop to the number alone, and the fold control shrinks: at a
 * phone's column width there is no room for "3 events" seven times over.
 */
@media (max-width: 640px) {
	.ts-pc-strip__day {
		gap: 0.25em;
		font-size: 0.68rem;
	}

	.ts-pc-strip__icon {
		display: inline-block;
	}

	.ts-pc-strip__label {
		display: none;
	}

	.event_calendar.fc,
	.fc.calendar {
		padding-right: 15px;
	}

	.ts-pc-week-toggle {
		width: 13px;
	}

	.ts-pc-strip__open {
		right: -14px;
		width: 13px;
	}

	.ts-pc-daystrip__time {
		font-size: 0.7em;
	}
}

/*
 * ---------------------------------------------------------------------------
 * Page layout
 * ---------------------------------------------------------------------------
 */

/*
 * The countdown belongs under the image, not above it, at every width.
 * The markup puts it first, so it is reordered rather than moved.
 */
#events-preview-box .grid-item-inner {
	display: flex;
	flex-direction: column;
}

#events-preview-box .media-box {
	order: 1;
}

#events-preview-box .preview-event-bar {
	order: 2;
	margin: 0;
}

/* This plugin's countdown, standing in for the theme's frozen one. */
#events-preview-box .ts-pc-preview__countdown {
	order: 2;
}

#events-preview-box .grid-content {
	order: 3;
}

/*
 * Register, share and directions on one line under the address.
 *
 * The theme gives this row a grey band of its own across the card. Beside a
 * tall picture that band began below the picture rather than below the
 * details, leaving a wide empty stripe with two small icons at its far end.
 * It reads as the closing line of the details instead — register first, as
 * the theme writes it, then the icons.
 */
#events-preview-box .grid-footer {
	order: 4;
	display: flex;
	align-items: center;
	flex-wrap: wrap;
	gap: 0.6em;
	margin: 0.8em 0 0;
	padding: 0;
	background: none;
}

#events-preview-box .grid-footer .action-buttons {
	display: flex;
	align-items: center;
	gap: 0.7em;
	margin: 0;
	padding: 0;
	list-style: none;
}

#events-preview-box .grid-footer .action-buttons > li {
	margin: 0;
	font-size: 17px;
	line-height: 1;
}

/*
 * Directions on a phone.
 *
 * The theme marks that one "hidden-xs", which the grid framework takes as an
 * instruction to drop it on a narrow screen -- the screen most likely to be
 * held by somebody who wants directions.
 */
#events-preview-box .grid-footer .action-buttons > li.hidden-xs {
	display: block !important;
}

/* This row places its own contents; nothing in it floats. */
#events-preview-box .grid-footer .btn,
#events-preview-box .grid-footer .pull-right {
	float: none;
	margin: 0;
}

/* Where else the same gathering is listed, as a footnote to all of it. */
#events-preview-box .ts-pc-preview__also {
	order: 5;
}

/*
 * The countdown reads as a line of text, not as a panel of boxes.
 *
 * The theme gives each unit its own bordered cell with the label beneath the
 * number, which in a narrow column wrapped onto a second line. Each unit is
 * now the number and its letter together — 1d 17h 30m 20s — on one line.
 */
#events-preview-box .counter-preview {
	display: flex;
	align-items: baseline;
	gap: 0.55em;
	background: none;
	border: 0;
	margin: 0;
	padding: 0;
	white-space: nowrap;
}

#events-preview-box .counter-preview .timer-col {
	display: inline-flex;
	align-items: baseline;
	gap: 0.1em;
	width: auto;
	min-width: 0;
	margin: 0;
	padding: 0;
	border: 0;
	background: none;
	color: inherit;
	font-size: 0.9em;
	line-height: 1.4;
	opacity: 0.7;
}

/*
 * Centred under the thumbnail on a wide screen, on its own faint band, and
 * close to the title beneath it — it was drifting left of the image with a
 * gap below that read as a break in the card.
 */
@media (min-width: 992px) {
	#events-preview-box .preview-event-bar {
		display: flex;
		justify-content: center;
		padding: 0.35em 0.5em;
		background: rgba(128, 128, 128, 0.09);
	}

	#events-preview-box .grid-content {
		padding-top: 0.5em;
	}
}

#events-preview-box .counter-preview .timer-type {
	display: inline;
	margin: 0;
	padding: 0;
	border: 0;
	font-size: 1em;
	text-transform: none;
}

/*
 * The preview on a phone.
 *
 * Columns stack below the medium breakpoint, which put the preview beneath a
 * full month of calendar where it went unnoticed. It leads instead, and the
 * thumbnail sits beside the details rather than above them — the theme lays
 * its preview out in a single column, which on a phone left a wide empty space
 * next to the image and pushed the title below the fold.
 */
@media (max-width: 991px) {
	.ts-pc-preview-row {
		display: flex;
		flex-direction: column;
	}

	.ts-pc-preview-col {
		order: -1;
		margin-bottom: 1em;
	}

	/*
	 * The theme's own preview, which is what a website event renders through.
	 *
	 * A grid rather than a row: the image and the countdown share the left
	 * column at the same width, one above the other, and the details take the
	 * right across both. The countdown sits in its own wrapper while the image
	 * and the details are its siblings, so a single flex row cannot place all
	 * three — laying it out on the wrapper is why the details stayed below.
	 */
	#events-preview-box .grid-item-inner {
		display: grid;
		grid-template-columns: 38% 1fr;
		align-items: start;
		/* No row gap: the countdown sits directly beneath its image. */
		gap: 0 0.9em;
	}

	#events-preview-box .media-box {
		grid-column: 1;
		grid-row: 1;
	}

	#events-preview-box .preview-event-bar,
	#events-preview-box .ts-pc-preview__countdown {
		grid-column: 1;
		grid-row: 2;
	}

	#events-preview-box .grid-content {
		grid-column: 2;
		grid-row: 1;
	}

	/* Across both columns, beneath the image and the details alike. */
	#events-preview-box .ts-pc-preview__also {
		grid-column: 1 / -1;
		grid-row: 3;
	}

	/* Fills the height the details set, cropping to centre. */
	#events-preview-box .media-box {
		max-width: none;
		align-self: stretch;
		min-height: 0;
		height: auto;
		overflow: hidden;
	}

	#events-preview-box .media-box img {
		width: 100%;
		height: 100%;
		object-fit: cover;
		object-position: center;
	}

	#events-preview-box .grid-content {
		/* Without this a long title stretches the column rather than wrapping. */
		min-width: 0;
	}

	/* Beside the picture the row starts where the address does, not at the end. */
	#events-preview-box .action-buttons {
		justify-content: flex-start;
	}

	/* This plugin's own preview, for a Planning Center or Google event. */
	.ts-pc-preview {
		display: flex;
		align-items: flex-start;
		flex-wrap: wrap;
		gap: 0.9em;
	}

	/*
	 * The links run under both the picture and the words, which share the row
	 * above. They belong to the event as a whole, and in the column beside the
	 * picture they had no width to speak of.
	 */
	.ts-pc-preview .ts-pc-preview__also {
		flex: 1 0 100%;
	}

	/*
	 * A filmstrip rather than a list: each calendar is a box of its own, side
	 * by side, and an event listed in four of them scrolls across instead of
	 * pushing the page down.
	 */
	.ts-pc-preview__also-track {
		display: flex;
		gap: 0.4em;
		overflow-x: auto;
		/*
		 * Locked to the one axis. A scroller left to itself takes the vertical
		 * as well, so a sideways drag drifted the strip up and down; and
		 * without the containment a drag that reaches the end carries on into
		 * the page behind it.
		 */
		overflow-y: hidden;
		touch-action: pan-x;
		overscroll-behavior-x: contain;
		scroll-behavior: smooth;
		scroll-snap-type: x proximity;
		-webkit-overflow-scrolling: touch;
		/* The bar would sit under the boxes and add height for nothing. */
		scrollbar-width: none;
	}

	.ts-pc-preview__also-track::-webkit-scrollbar {
		display: none;
	}

	.ts-pc-preview__also.is-scrollable .ts-pc-preview__also-nav {
		display: inline-flex;
		align-items: center;
		justify-content: center;
	}

	/*
	 * A set width rather than one taken from the words: the boxes then read as
	 * a row of equal cards, and a long event name cannot stretch one of them
	 * across the whole strip.
	 */
	.ts-pc-preview__also .ts-pc-preview__chip {
		flex: 0 0 auto;
		width: 12.5em;
		max-width: 72vw;
		margin: 0;
		padding: 0.45em 0.7em;
		scroll-snap-align: start;
	}

	/*
	 * The mark carries the calendar's name on the top line, so the words are
	 * dropped: "View in [Church Center] >" in the width of a thumb. What the
	 * calendar calls the event, and when, stay underneath.
	 */
	.ts-pc-preview__also .ts-pc-preview__chip-name {
		display: none;
	}

	.ts-pc-preview__also .ts-pc-preview__chip em {
		margin-top: 0.2em;
		font-size: 0.78em;
	}

	.ts-pc-preview__also .ts-pc-preview__chip-lead {
		order: 1;
	}

	.ts-pc-preview__also .ts-pc-preview__chip-mark {
		order: 2;
		/* Between the words and the arrow here, so it needs no lead of its own. */
		margin-right: 0;
	}

	.ts-pc-preview__also .ts-pc-preview__chip-chev {
		order: 3;
	}

	.ts-pc-preview__also .ts-pc-preview__chip-line {
		gap: 0.4em;
		white-space: nowrap;
	}

	.ts-pc-preview__media {
		flex: 0 0 38%;
		max-width: 38%;
	}

	.ts-pc-preview__image {
		height: 150px;
		margin-bottom: 0;
		overflow: hidden;
	}

	.ts-pc-preview__image img {
		width: 100%;
		height: 100%;
		object-fit: cover;
		object-position: center;
	}

	.ts-pc-preview__body {
		flex: 1 1 auto;
		min-width: 0;
	}

	.ts-pc-preview__title {
		font-size: 1.05em;
	}
}

/*
 * The toolbar on a phone.
 *
 * Wrapping put the arrows and Today on a second line and pushed the calendar
 * itself below the fold. Everything shrinks enough to stay on one.
 */
@media (max-width: 640px) {
	.fc-toolbar,
	.fc .fc-toolbar {
		flex-wrap: nowrap;
		gap: 0.35em;
		padding: 0.35em 0.4em;
	}

	.fc-toolbar h2 {
		font-size: 1.05em;
		gap: 0.2em;
		padding: 0;
	}

	/* Keeps the buttons inside the toolbar rather than over its edge. */
	.fc-toolbar .fc-left {
		min-width: 0;
		overflow: hidden;
	}

	.fc-toolbar .fc-right {
		flex: 0 0 auto;
		margin-left: auto;
	}

	.ts-pc-pick__field {
		font-size: 1em;
	}

	.ts-pc-pick--zone .ts-pc-pick__field {
		font-size: 0.65rem;
	}

	.fc .fc-toolbar .fc-button,
	.fc-toolbar .fc-button {
		padding: 0.25em 0.45em;
		height: auto;
		line-height: 1.3;
		font-size: 0.8em;
	}

	/* The title yields first, since the buttons cannot shrink much further. */
	.fc-toolbar .fc-center {
		min-width: 0;
		overflow: hidden;
	}

	.fc-toolbar .fc-left,
	.fc-toolbar .fc-right {
		flex: 0 0 auto;
	}
}

/*
 * ---------------------------------------------------------------------------
 * Toolbar and countdown: explicit sizes
 *
 * The theme styles headings and buttons site-wide, and repeated attempts to
 * size this bar were quietly overridden. These are stated in pixels and marked
 * important so nothing further up can win — blunt, but the alternative has been
 * changes that read as correct and have no effect on the page.
 * ---------------------------------------------------------------------------
 */
.fc .fc-toolbar,
.fc-toolbar {
	display: flex !important;
	align-items: center !important;
	min-height: 0 !important;
	height: auto !important;
	padding: 6px 10px !important;
	margin-bottom: 10px !important;
	border: 0 !important;
	background-image: none !important;
}

/*
 * The padding lives on the sections, not on the bar: the theme sets 20px
 * around the title and 28px above the buttons. That is where the height came
 * from, and setting it on the bar alone never touched it.
 */
.fc .fc-toolbar .fc-left,
.fc .fc-toolbar .fc-center,
.fc .fc-toolbar .fc-right {
	display: flex !important;
	align-items: center !important;
	float: none !important;
	margin: 0 !important;
	padding: 0 !important;
	min-height: 0 !important;
}

/*
 * The sections are appended left, right, centre. Ordering them puts the empty
 * middle back between the two, where its slack pushes the buttons to the end
 * instead of stranding them beside the title.
 */
/* Allowed to shrink, so a narrow screen clips the title rather than the bar. */
.fc .fc-toolbar .fc-left {
	order: 1 !important;
	flex: 0 1 auto !important;
	min-width: 0 !important;
}

.fc .fc-toolbar .fc-center {
	order: 2 !important;
	flex: 1 1 auto !important;
}

.fc .fc-toolbar .fc-right {
	order: 3 !important;
	flex: 0 0 auto !important;
}

.fc .fc-toolbar .fc-clear {
	display: none !important;
}

.fc .fc-toolbar h2 {
	display: flex !important;
	align-items: center !important;
	gap: 6px !important;
	font-size: 20px !important;
	line-height: 30px !important;
	height: 30px !important;
	margin: 0 !important;
	padding: 0 !important;
}

.fc .fc-toolbar .fc-button {
	height: 30px !important;
	min-height: 0 !important;
	line-height: 28px !important;
	padding: 0 10px !important;
	margin: 0 !important;
	font-size: 13px !important;
	box-shadow: none !important;
}

.fc .fc-toolbar .fc-button-group {
	display: flex !important;
	align-items: center !important;
	margin: 0 6px 0 0 !important;
}

/*
 * Today wears the colour of the ring it takes you to: underlined at rest, and
 * the line closing into a full border on hover. The border is there at rest as
 * well, transparent on three sides, so nothing shifts when it appears.
 *
 * Never dimmed: the library switches this button off inside the current month,
 * where it still has work to do.
 */
.fc .fc-toolbar .fc-today-button,
.fc .fc-toolbar .fc-today-button.fc-state-disabled {
	border: 2px solid transparent !important;
	border-bottom-color: rgba(226, 178, 26, 0.9) !important;
	border-radius: 3px !important;
	background: none !important;
	opacity: 1 !important;
	cursor: pointer !important;
	transition: border-color 0.15s ease, background-color 0.15s ease !important;
}

.fc .fc-toolbar .fc-today-button:hover,
.fc .fc-toolbar .fc-today-button:focus {
	border-color: rgba(226, 178, 26, 0.9) !important;
	background: rgba(226, 178, 26, 0.1) !important;
	outline: none !important;
}

.fc .fc-toolbar .ts-pc-pick__field {
	height: 30px !important;
	line-height: 30px !important;
	padding: 0 !important;
}

/* Centred under the thumbnail, with nothing hanging below it. */
#events-preview-box .ts-pc-preview__countdown,
.ts-pc-preview__countdown {
	display: block !important;
	width: 100% !important;
	margin: 0 !important;
	padding: 5px 8px !important;
	text-align: center !important;
	line-height: 1.3 !important;
}

@media (max-width: 640px) {
	.fc .fc-toolbar {
		padding: 5px 6px !important;
		gap: 4px !important;
	}

	.fc .fc-toolbar h2 {
		font-size: 15px !important;
		line-height: 26px !important;
		height: 26px !important;
		gap: 3px !important;
	}

	.fc .fc-toolbar .fc-button {
		height: 26px !important;
		line-height: 24px !important;
		padding: 0 6px !important;
		font-size: 11px !important;
	}

	.fc .fc-toolbar .ts-pc-pick__field {
		height: 26px !important;
		line-height: 26px !important;
		font-size: 15px !important;
	}

	.fc .fc-toolbar .fc-button-group {
		margin-right: 3px !important;
	}
}

/*
 * ---------------------------------------------------------------------------
 * A page with no banner
 *
 * The header is taken out of the flow and a banner normally fills the space
 * beneath it, so the theme adds its own padding on top of that. With no banner
 * the script measures and reserves exactly the header's height, and the
 * theme's padding is then doubling up. Marked important because the theme
 * writes this value into a style block inside the body, which outranks a
 * stylesheet on order alone.
 * ---------------------------------------------------------------------------
 */
.ts-pc-no-banner .content,
.ts-pc-no-banner .content.full {
	padding-top: 0 !important;
}

.ts-pc-no-banner #content-col,
.ts-pc-no-banner .post-content {
	padding-top: 0 !important;
}

/*
 * The calendar's own heading.
 *
 * "Event Preview" is printed by the theme's calendar shortcode, not written on
 * the page, and it labels a panel that already says what it is.
 */
.ts-pc-preview-col > h2.title {
	display: none !important;
}

/*
 * ---------------------------------------------------------------------------
 * The theme's event widgets
 *
 * These list the same gatherings the calendar does, so they carry the same
 * marks: one per other calendar the event is listed in, beside its name. The
 * rest of the item is the theme's own markup and keeps the theme's styling.
 * ---------------------------------------------------------------------------
 */
.ts-pc-widget__marks {
	display: inline-flex;
	align-items: center;
	gap: 4px;
	margin-left: 0.45em;
	vertical-align: middle;
}

.ts-pc-widget__mark {
	position: static;
	display: inline-flex;
	align-items: center;
	justify-content: center;
	/*
	 * Holds its size. A flex item may be shrunk below the width it asks for,
	 * and the drawing inside it may not, so in a narrow column the marks were
	 * squeezed until each one was drawn over the next.
	 */
	flex: 0 0 auto;
	width: 15px;
	height: 15px;
	opacity: 0.55;
}

.ts-pc-widget__item:hover .ts-pc-widget__mark {
	opacity: 1;
}

.ts-pc-widget__mark svg {
	flex: 0 0 auto;
	width: 15px;
	height: 15px;
	fill: currentColor;
	stroke: none;
}

/* Google's mark is drawn larger than Planning Center's; evened up here. */
.ts-pc-widget__mark.ts-pc-badge--google svg {
	width: 13px;
	height: 13px;
}

/*
 * The heading line of the wide list block.
 *
 * The theme prints its "all events" button before the heading and floats it
 * right, which leaves it stranded on a line of its own above the heading. They
 * share a line here, the heading keeping the left.
 */
.ts-pc-widget__head {
	display: flex !important;
	align-items: center !important;
	justify-content: space-between !important;
	/*
	 * Never wraps. The theme's heading carries forty pixels of margin below it
	 * and the two together outgrew the column, which dropped the button onto a
	 * line of its own -- the very thing this is here to prevent.
	 */
	flex-wrap: nowrap !important;
	gap: 1em;
	margin-bottom: 1.4em;
}

/* Scoped past .panel-grid h3.panel-title, which sets that margin. */
.panel-grid .ts-pc-widget__head h3.panel-title,
.ts-pc-widget__head .panel-title {
	flex: 0 1 auto;
	width: auto;
	margin: 0 !important;
}

.ts-pc-widget__head .ts-pc-widget__all {
	flex: 0 0 auto;
	float: none;
	margin: 0;
}

/*
 * Compact date blocks.
 *
 * The theme's are a hundred pixels square, which suits a page of a few events
 * with pictures. In a list they take a quarter of the width and leave the
 * details crowded into what is left.
 */
.ts-pc-widget .event-list-item-date {
	width: auto;
	margin-right: 14px;
}

.ts-pc-widget .event-list-item-date .event-date {
	width: 56px;
	height: 56px;
	margin-top: 2px;
	border-width: 1px;
	border-radius: 3px;
	/* The dashed tile reads as noise at this size. */
	background-image: none;
	background-color: rgba(128, 128, 128, 0.08);
}

.ts-pc-widget .event-list-item-date .event-day {
	padding-top: 7px;
	font-size: 24px;
	line-height: 1;
	color: inherit;
}

.ts-pc-widget .event-list-item-date .event-month {
	font-size: 11px;
	line-height: 1.2;
}

/* The details take the room the date gave back. */
.ts-pc-widget .event-list-item-info,
.ts-pc-widget .event-list-item-info-nometa {
	float: none;
	width: auto;
	overflow: hidden;
	padding-bottom: 0.9em;
	padding-right: 0;
	border-right: 0;
	margin-right: 0;
}

.ts-pc-widget .event-list-item + .event-list-item {
	margin-top: 0.2em;
}

/*
 * Time on one line, place on the next.
 *
 * The theme runs these together as inline spans, which on a narrow column
 * wove the address through the times and left neither readable at a glance.
 */
.ts-pc-widget .meta-data {
	display: block;
	margin-top: 0.25em;
}

/*
 * Scoped through the container so it outranks the rule above, which sets
 * every meta line to block -- as a block the clamped address became a box of
 * its own and dropped below its icon.
 */
.ts-pc-widget .ts-pc-widget__where {
	display: flex;
	align-items: flex-start;
	gap: 0.45em;
}

.ts-pc-widget .ts-pc-widget__where .fa {
	/* Level with the first line of the address rather than its middle. */
	margin-top: 0.28em;
}

/* Two lines, then trimmed. The full address is on the element's title. */
.ts-pc-widget .ts-pc-widget__where-text {
	display: -webkit-box;
	-webkit-line-clamp: 2;
	-webkit-box-orient: vertical;
	overflow: hidden;
}

.ts-pc-widget__when .label {
	margin-left: 0.4em;
}

/*
 * The whole entry opens the event.
 *
 * Done by stretching the title's own link across the entry rather than by
 * wrapping everything in an anchor or listening for clicks: there is still one
 * link, it is still the title, and it still reads and tabs as one thing. The
 * address and the calendar marks sit above it and keep their own destinations.
 */
.ts-pc-widget__item {
	position: relative;
}

.ts-pc-widget__item .lined-info h4 a::after {
	content: "";
	position: absolute;
	inset: 0;
	z-index: 1;
}

.ts-pc-widget__item .ts-pc-widget__where-text,
.ts-pc-widget__item .ts-pc-widget__mark {
	position: relative;
	z-index: 2;
}

/*
 * The corner offsets belong to the calendar's badges, where they are pinned
 * inside an entry. Made relative above, a mark started obeying them and drifted
 * off its line.
 */
.ts-pc-widget__item .ts-pc-widget__mark {
	top: auto;
	right: auto;
}

.ts-pc-widget .ts-pc-widget__marks {
	flex-wrap: nowrap;
	gap: 6px;
}

/* The entry answers to the pointer as a whole. */
.ts-pc-widget__item:hover {
	cursor: pointer;
}

.ts-pc-widget__item:hover .lined-info h4 a {
	text-decoration: underline;
}

.ts-pc-widget .ts-pc-widget__where-text {
	color: inherit;
	text-decoration: none;
}

.ts-pc-widget .ts-pc-widget__where-text:hover,
.ts-pc-widget .ts-pc-widget__where-text:focus {
	text-decoration: underline;
}