//! The two design-system sheets the public embeds inline.
//!
//! What used to be here as well were five Askama templates, one per embed, each
//! carrying a hand-written `<style>` block. They are gone: `54d7f8cf`, and the
//! screens they drew are described in `crate::quasi::embeds` now. What survives
//! is the pair of generated sheets, because the reason an embed inlines its
//! design system did not change with how the embed is drawn.

/// The spacing layer the embeds inline, written by `build.rs` from
/// makeover-geometry at Pointer density.
///
/// An embed cannot link a stylesheet: it renders inside an iframe on somebody
/// else's page, so its whole design system has to arrive in the document. That
/// is why these five templates carry a `<style>` block when nothing else in the
/// tree does. What it must not mean is that the values were copied by hand,
/// which is what it meant until this existed.
pub const EMBED_GEOMETRY_CSS: &str = include_str!("../../static/embed-geometry.css");

/// The typography layer, inlined for the same reason as the spacing one.
///
/// Its own file, like geometry's, and for a reason of the same shape: geometry
/// differs because an embed runs at Pointer density with no `@media` block,
/// and typography differs because **an embed carries the house slots and not
/// MNW's brand override**. Young Serif reaches the site through layer 0, but an
/// embed leaves `--font-display` undefined so the
/// `var(--font-display, Georgia, serif)` fallback in each template renders.
/// That is the older decision unchanged, now stated as a second `Typography`
/// rather than as a token nobody defined; both files come out of one
/// vocabulary in build.rs, so they cannot drift on the slots they share.
///
/// The `@font-face` URLs are absolute (`/static/fonts/...`) and the iframe's
/// document is served from this origin, so they resolve here rather than
/// against the host page.
///
/// **This makes an embed fetch 81 KB of font on somebody else's page**, which
/// is a cost the host author did not choose, so it is worth saying why it is
/// the right call. The five templates named `Lato` and `IBM Plex Mono` as
/// literals and neither face was ever declared in an embed document, so every
/// one of them has been rendering in `-apple-system` and the host's default
/// monospace since they were written: the literals described an intention
/// nothing implemented. The choice is therefore between an embed that looks
/// like our product and one that looks like whatever the visitor's browser
/// prefers, and it is not close. `font-display: swap` keeps the card readable
/// while the faces arrive.
pub const EMBED_TYPOGRAPHY_CSS: &str = include_str!("../../static/embed-typography.css");

/// The colour layer for an embed: the platform default theme, resolved through
/// makeover the same way every page's is.
///
/// Always the default. Serving a creator's chosen theme into a third-party page
/// is a separate product question, and this is not the place to answer it by
/// accident.
pub fn embed_theme_css() -> &'static str {
    crate::theming::theme_css(None)
}