/* ==========================================================================
   GDCONF Substack Feed block
   ========================================================================== */

.gdconf-substack-feed {
	list-style: disc;
	padding-left: 1.4em;
	margin: 0;
}

.gdconf-substack-feed__item {
	margin-bottom: 1.1em;
	line-height: 1.5;
}
.gdconf-substack-feed__item:last-child {
	margin-bottom: 0;
}

.gdconf-substack-feed__title {
	display: block;
	font-size: 1em;
	font-weight: 500;
	color: var(--theme-palette-color-1, #2563eb);
	text-decoration: none;
	line-height: 1.4;
}
.gdconf-substack-feed__title:hover {
	text-decoration: underline;
}

.gdconf-substack-feed__meta {
	font-size: 0.85em;
	color: #475569;
	margin-top: 2px;
}

[data-color-mode*="dark"] .gdconf-substack-feed__meta {
	color: #94a3b8;
}
@media (prefers-color-scheme: dark) {
	:root:not([data-color-mode]) .gdconf-substack-feed__meta,
	:root[data-color-mode="os-default"] .gdconf-substack-feed__meta {
		color: #94a3b8;
	}
}

/* === generated: dark mode when the site follows the OS === */
/* Blocksy writes data-color-mode="os-default" when the visitor has not
   picked a mode and the site simply follows their device. Every rule above
   is keyed on ="dark" and so missed that case entirely: on a phone set to
   dark, the page went dark while these stayed light - which is how striped
   rows ended up painted near-white on a dark table.

   This block mirrors them for the follow-the-OS case, and for a theme that
   sets no attribute at all. It is generated, and a test asserts every dark
   rule above has both twins here, so the two cannot drift apart. Edit the
   rules above, then regenerate. */
@media (prefers-color-scheme: dark) {
		:root[data-color-mode="os-default"] .gdconf-substack-feed__meta,
		:root:not([data-color-mode]) .gdconf-substack-feed__meta {
	color: #94a3b8;
		}
}