unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: 69432@debbugs.gnu.org
Cc: "Ludovic Courtès" <ludo@gnu.org>, pelzflorian@pelzflorian.de
Subject: [bug#69432] [PATCH guix-artwork v2 2/3] website: Use Fira Sans for section headings only.
Date: Thu, 29 Feb 2024 22:47:13 +0100	[thread overview]
Message-ID: <20240229214714.9431-2-ludo@gnu.org> (raw)
In-Reply-To: <20240229214714.9431-1-ludo@gnu.org>

With commit b7ccc5cb1b4ec936c00dbd98376c5d2677e60a63, Fira Sans was used
for the body of sections, not just section headings.  This is what
<https://www.gnu.org/software/gnulib/manual.css> prescribes but it’s not
what was intended.

* website/static/base/css/manual.css: Add rule.
---
 website/static/base/css/manual.css | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/website/static/base/css/manual.css b/website/static/base/css/manual.css
index 8ecd872..8970457 100644
--- a/website/static/base/css/manual.css
+++ b/website/static/base/css/manual.css
@@ -323,6 +323,13 @@ h1.settitle, h1.top, h2.chapter, h3.section, h4.subsection, h4.subsubsection {
     font-weight: bold;
 }
 
+/* Use a serif font for section bodies (this overrides /gnulib/manual.css,
+   which currently applies to entire section classes, as opposed to section
+   classes for headings only).  */
+div.settitle, div.top, div.chapter, div.section, div.subsection, div.subsubsection {
+    font-family: serif;
+}
+
 /* Texinfo footnotes are in a "footnote" <div> but each of them is
    wrapped in <h5> (go figure).  Have them use a regular font instead
    of bold.  */
-- 
2.41.0





  reply	other threads:[~2024-02-29 21:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-27 16:51 [bug#69432] [PATCH 0/3] Change fonts of the on-line manual Ludovic Courtès
2024-02-27 21:38 ` pelzflorian (Florian Pelz)
2024-02-27 21:38 ` [bug#69432] [PATCH 1/3] website: Adjust style of web site builder Ludovic Courtès
2024-02-27 21:38   ` [bug#69432] [PATCH 2/3] website: Use Fira Sans for section headings only Ludovic Courtès
2024-02-27 21:38   ` [bug#69432] [PATCH 3/3] website: Use Linux Libertine for the body of the manual Ludovic Courtès
2024-02-28  7:56     ` pelzflorian (Florian Pelz)
2024-02-29 21:41       ` Ludovic Courtès
2024-02-29 21:47         ` [bug#69432] [PATCH guix-artwork v2 1/3] website: Adjust style of web site builder Ludovic Courtès
2024-02-29 21:47           ` Ludovic Courtès [this message]
2024-02-29 21:47           ` [bug#69432] [PATCH guix-artwork v2 3/3] website: Use Linux Libertine for the body of the manual Ludovic Courtès
2024-03-01 11:51             ` pelzflorian (Florian Pelz)
2024-03-02 15:01               ` bug#69432: " Ludovic Courtès
2024-02-28  8:06   ` [bug#69432] [PATCH 1/3] website: Adjust style of web site builder pelzflorian (Florian Pelz)

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240229214714.9431-2-ludo@gnu.org \
    --to=ludo@gnu.org \
    --cc=69432@debbugs.gnu.org \
    --cc=pelzflorian@pelzflorian.de \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).