unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: sirgazil <sirgazil@zoho.com>
Cc: 39635@debbugs.gnu.org, Luis Felipe <luis.felipe.la@protonmail.com>
Subject: [bug#39635] [PATCH] website: Modify use of H1 headings
Date: Thu, 08 Oct 2020 22:49:17 -0400	[thread overview]
Message-ID: <87a6wwru4y.fsf@gmail.com> (raw)
In-Reply-To: <20200216182649.25068-1-sirgazil@zoho.com> (sirgazil@zoho.com's message of "Sun, 16 Feb 2020 13:26:49 -0500")

Hello sirgazil!

sirgazil <sirgazil@zoho.com> writes:

> The website was originally designed to use only one H1 element per
> page, which is/was seen as a best practice for accessibility and
> SEO. However, the value of the H1 element in all the pages of the
> website was always the alternative text of the Guix logo ("Guix"). The
> main content of a page started with a level 2 heading (H2).
>
> This change maintains the best practice of using only one H1 element
> per page, but gives a less important level to the Guix logo (it
> becomes H2) and uses H1 as the heading for the main content of
> pages. This means, for example, that the H1 of the download page is
> "Download", the H1 of the help page is "Help", the H1 of a blog post
> is its title, and so on.
>
> The changes were tested in the following browsers (without assistive
> technologies):
>
> * IceCat 68.4.1esr
> * Epiphany 3.32.5 (WebKitGTK+ 2.26.3)
> * Lynx 2.8.9rel.1

Thanks for the patch!  It makes sense.  Unfortunately it doesn't apply
with 'git am' :-/.  Could you rebase it on the current master branch of
guix-artwork?

Thank you,

Maxim




  parent reply	other threads:[~2020-10-09  2:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-16 18:26 [bug#39635] [PATCH] website: Modify use of H1 headings sirgazil via Guix-patches via
2020-10-06 14:03 ` [bug#39635] " Luis Felipe via Guix-patches via
2020-10-09  2:49 ` Maxim Cournoyer [this message]
2020-10-10 19:51   ` [bug#39635] [PATCH] " Luis Felipe via Guix-patches via
2020-10-12  8:02     ` zimoun
2020-10-12 14:08       ` Luis Felipe via Guix-patches via
2020-10-13  1:36     ` Maxim Cournoyer
2022-10-18 15:58     ` zimoun
2022-10-18 21:34       ` Luis Felipe via Guix-patches via

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=87a6wwru4y.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=39635@debbugs.gnu.org \
    --cc=luis.felipe.la@protonmail.com \
    --cc=sirgazil@zoho.com \
    /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).