/*
 * All that is left of Frontend Meetings' own stylesheet.
 *
 * The screen is Tailwind now, including the header action and the cross-link
 * that were the last two rules here. What remains cannot be a utility: it
 * reaches into a shared component's own class from an ancestor context, which
 * is the one thing a utility cannot do.
 */

/*
 * The empty state, un-nested.
 *
 * `.gmt-am` is written to be the page column on All Meetings: 1420px cap, 40px
 * gutter, sitting straight under the mount. Here it sits inside
 * `.settings-container`, which is the same column with the same gutter - so the
 * two stacked and the panel came out 1240px against All Meetings' 1320px, 80px
 * narrower on the next menu item down.
 *
 * The gutter belongs to the outer element, which is the same conclusion
 * `.gmt-admin-settings-container` reached when Platform Settings nested the
 * same pair. Measured before and after: 1240px, then 1320px, matching.
 */
.settings-container .gmt-am {
    max-width: none;
    padding-left: 0;
    padding-right: 0;
}

/*
 * The same empty state inside Settings → Frontend form, where the settings
 * page already supplies the column and the gutter.
 */
.gmt-settings-section .gmt-am {
    max-width: none;
    padding-left: 0;
    padding-right: 0;
}