From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from atuin.qyliss.net (localhost [IPv6:::1]) by atuin.qyliss.net (Postfix) with ESMTP id 21EDFA593; Wed, 27 May 2026 12:40:27 +0000 (UTC) Received: by atuin.qyliss.net (Postfix, from userid 993) id B2FDBA4D7; Wed, 27 May 2026 12:40:24 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-26) on atuin.qyliss.net X-Spam-Level: X-Spam-Status: No, score=0.4 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,DMARC_MISSING,FROM_SUSPICIOUS_NTLD,SPF_HELO_NONE, T_PDS_OTHER_BAD_TLD autolearn=no autolearn_force=no version=4.0.1 Received: from mail-108-mta230.mxroute.com (mail-108-mta230.mxroute.com [136.175.108.230]) by atuin.qyliss.net (Postfix) with ESMTPS id D8DA9A4D4 for ; Wed, 27 May 2026 12:40:22 +0000 (UTC) Received: from filter006.mxroute.com ([136.175.111.3] filter006.mxroute.com) (Authenticated sender: mN4UYu2MZsgR) by mail-108-mta230.mxroute.com (ZoneMTA) with ESMTPSA id 19e69733b1500067f7.002 for (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384); Wed, 27 May 2026 12:40:19 +0000 X-Zone-Loop: 4103c5879658b178413a5de1340fbe6bdc813f9d5413 X-Originating-IP: [136.175.111.3] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gagarin.work; s=x; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: From:References:Cc:To:Subject:MIME-Version:Date:Message-ID:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=lvvsEs0WvLE7vwZmYkRcNkBLAXvz+5B7y9YNWrzz42I=; b=bhhMYtrRGE1KDKwEroc3Sa3tH5 e4yXC8dP/qE+Hoxzm1kaOTwjrM1Va8CpWHfkyIUbCIlB764ViWCNt6kIcHqJvw4HhHpZuGXixCNCz QI74k3ES5KCaaElEjmHe+NsRW9K5tmTqJBl3SU8MFAO7WSPZ32JqcR3PHiFT3zXxil2I+jlaxSHGc XRwxfu1F3Wqa41GrzqEWo60KfKYRroH2JUvWClRSBRUgkGbvHgN9f4Trbg3xy2F6qsLnbr0LuukCH SH5s0plrUCtKxiDOBtPNa3gFFa50+fNTVIkKZqItoEwXEhUbn3dbTUaa630uSPrFxMle5LwRQ6S/L +CJRkQ7w==; Message-ID: <31f75148-1b63-4d46-9821-2edb1bfa1c12@gagarin.work> Date: Wed, 27 May 2026 14:40:16 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v5] Documentation: add logo to site header To: Alyssa Ross References: <20260520085723.135653-1-valentin@gagarin.work> <20260527112408.14580-1-valentin@gagarin.work> <8733zdgitd.fsf@alyssa.is> Content-Language: en-US From: Valentin Gagarin In-Reply-To: <8733zdgitd.fsf@alyssa.is> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-Id: valentin@gagarin.work Message-ID-Hash: EFXSTWHNHLPVHWQIDMA2TDZYGQOFWB6U X-Message-ID-Hash: EFXSTWHNHLPVHWQIDMA2TDZYGQOFWB6U X-MailFrom: valentin@gagarin.work X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-devel.spectrum-os.org-0; header-match-devel.spectrum-os.org-1; header-match-devel.spectrum-os.org-2; header-match-devel.spectrum-os.org-3; header-match-devel.spectrum-os.org-4; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: devel@spectrum-os.org X-Mailman-Version: 3.3.9 Precedence: list List-Id: Patches and low-level development discussion Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: > We should pick (and document) a preferred order! Agreed and noted for later. >> .main-content { >> // Just the Docs puts titles next to definitions, rather than on >> @@ -20,3 +21,23 @@ >> margin-left: 2ch; >> } >> } >> + >> +// Make the logo and title fit the site header. >> +.site-header { >> + .site-logo { >> + width: 3rem; >> + } >> + >> + // Just the Docs displays a sidebar at the "medium size" `md` breakpoint and above. >> + // Use the upstream `mq` media query mixin to target that breakpoint. >> + // https://just-the-docs.com/docs/utilities/responsive-modifiers/ >> + // https://github.com/just-the-docs/just-the-docs/blob/v0.10.1/_sass/support/mixins/_layout.scss#L3-L8 >> + @include mq(md) { >> + .site-logo { >> + width: 5.5rem; >> + } > > Is there a reason for this number, rather than just setting it back to > 100%? Yes, because 100% means different things for different screen sizes. The media queries seem to be used inconsistently upstream; different elements shift at different breakpoints... That may or may not be fixed by bumping the dependency, but that currently is precluded by build failures. Keeping the font size and logo size fixed doesn't produce surprises. I recommend not to put too much energy into this in any case. Aligning the output style across the current website and "the docs" will likely make this obsolete one way or another eventually.