/**
 * Frontend styles of the profile template (Team Custom).
 *
 * Loaded only on single team member views that actually use a template page,
 * see Profile_Template::enqueue_frontend_assets().
 *
 * Deliberately small: the layout is built with core blocks in the template
 * page, so column, spacing and colour styles come from there and from the
 * block editor. Only the block wrapper itself is styled here.
 */

.team-custom-profile__comments {
	margin-top: 2em;
}

/*
 * The wrapper is a block level element (div), so that the alignment controls
 * of the editor work: "wide" and "full" leave the text flow.
 *
 * Deliberately no display:inline-block here - it would cancel out the
 * alignwide/alignfull classes and the profile layout would break.
 */
.team-custom-profile-field {
	max-width: 100%;
}

/*
 * Opt-in variant for cases where several fields should sit next to each other.
 * Not the default, because it conflicts with the alignment controls.
 */
.team-custom-profile-field.is-inline {
	display: inline-block;
	margin-right: 1em;
}

.team-custom-profile-field__label {
	margin-right: 0.35em;
	font-weight: 600;
}

.team-custom-profile-field__link {
	text-decoration: inherit;
}

/*
 * Contact file (vCard) block.
 *
 * Without --button the link stays a plain link and inherits the typography of
 * the profile page. With --button it is laid out as one element next to the
 * block, so the theme styles it like the other links of the profile. Colour,
 * font size and spacing come from the block supports of the block itself.
 */
.team-custom-vcf__link {
	text-decoration: inherit;
}

.team-custom-vcf--button .team-custom-vcf__link {
	display: inline-block;
}

/*
 * Multiline fields ("Sprechzeiten"): the value is escaped plain text with <br>
 * between the lines, so the only thing left to style is the spacing between two
 * entries.
 */
.team-custom-profile-field--multi br {
	line-height: 1.6;
}

/*
 * Rich text fields (the ones from the classic editor: "Lehrveranstaltungen",
 * "Publikationen", ...) render their own paragraphs and lists. The first and
 * last child usually keep a margin, which would add a visible gap against the
 * surrounding blocks of the profile page.
 */
.team-custom-profile-field--rich > :first-child {
	margin-top: 0;
}

.team-custom-profile-field--rich > :last-child {
	margin-bottom: 0;
}

/*
 * Nested lists of the classic editor are indented by ul/ol inside ul/ol.
 * Without this the nested levels run into each other in a narrow profile
 * column.
 */
.team-custom-profile-field--rich ul ul,
.team-custom-profile-field--rich ol ol,
.team-custom-profile-field--rich ul ol,
.team-custom-profile-field--rich ol ul {
	margin-top: 0.25em;
}