From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Subject: [PATCH htdocs] tighten up margins on smaller devices
Date: Fri, 15 Dec 2023 21:10:29 -0500 [thread overview]
Message-ID: <20231216021029.22184-1-vapier@gentoo.org> (raw)
Scale down the font size and margins on headers on smaller devices.
The defaults cause the GDB title to take up most of the screen, and
then the links & page intro take up the rest. Scale down the font
so that it's still relatively larger, and tighten up the margins.
The content is still comfortably readable.
Similarly, tighten the spacing on lists -- the default can quickly
suck up horizontal space. The result is still clear how things are
broken up, but given more space for reading content.
---
css/site.css | 44 ++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 44 insertions(+)
diff --git a/css/site.css b/css/site.css
index 886dcccb3b0a..985fbde6e888 100644
--- a/css/site.css
+++ b/css/site.css
@@ -3,6 +3,7 @@
body {
background-color: #FFF;
color: #000;
+ margin: 0 0.5em 0 0.5em;
}
a:link {
@@ -43,3 +44,46 @@ a:visited {
img#archer-logo {
max-width: 25%;
}
+
+/* This is ~768px with 16pt font. */
+@media only screen and (max-width: 50em) {
+ h1 {
+ font-size: 1.5em;
+ }
+
+ h2 {
+ font-size: 1.3em;
+ }
+
+ h3 {
+ font-size: 1.1em;
+ }
+
+ h1, h2, h3, h4 {
+ margin: 0.5em 0 0.5em 0;
+ }
+}
+
+/* This is ~480px with 16pt font. */
+@media only screen and (max-width: 30em) {
+ h1 {
+ font-size: 1.3em;
+ }
+
+ h2 {
+ font-size: 1.2em;
+ }
+
+ ul {
+ padding-left: 1em;
+ }
+
+ dd {
+ margin-left: 1em;
+ }
+
+ /* How many spaces-per-tab. */
+ pre {
+ tab-size: 4;
+ }
+}
--
2.43.0
next reply other threads:[~2023-12-16 2:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-16 2:10 Mike Frysinger [this message]
2023-12-22 15:50 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231216021029.22184-1-vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).