From: Canan Talayhan <canan.t.talayhan@gmail.com>
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org
Subject: Re: [Outreachy] - Guix Data Service - Set a more informative page title
Date: Fri, 16 Apr 2021 12:58:00 +0300 [thread overview]
Message-ID: <CAAosC5Ky5i=dCKjYvbDTA_4Uo6QvrW1ykRXCMkvXSG2JPR=kVg@mail.gmail.com> (raw)
In-Reply-To: <87tuo7xljp.fsf@cbaines.net>
Hi again,
@Chris
After your suggestions, I've fixed the patch. But for the revision
part, I have a question. You said "I'd put "Channel News Entries"
first, then the Revision bit second." There are so many titles like
this structure in Revision views.
For example :
->System tests Revision c7d0441
or
->Revision c7d0441 System tests
Should I fix all of them this way? Or just for Channel News Entries?
I've set the rule for 80 chars. Thanks. :)
On Fri, Apr 16, 2021 at 12:52 AM Christopher Baines <mail@cbaines.net> wrote:
>
>
> Canan Talayhan <canan.t.talayhan@gmail.com> writes:
>
> > Hi team,
> >
> > Thanks for your help.
> >
> > @Chris
> > After all the modifications that I've made according to your comments,
> > I've created the latest version of my patch.
> > Could you please review the patch attached and share your ideas?
> >
> > Please note that a few parts are left. After your confirmation, I can
> > handle it shortly.
>
> Thanks Canan, I've had a quick look:
>
> > +(define page-header "Dumps")
> > +
> > (define (view-dumps available-dumps)
> > (layout
> > + #:title
> > + page-header
> > #:body
> > `(,(header)
> > (div
> > @@ -31,7 +35,7 @@
> > (@ (class "row"))
> > (div
> > (@ (class "col-sm-12"))
> > - (h1 "Database dumps")))
> > + (h1 ,page-header)))
>
> I'd generally stick with more descriptive titles, "Database dumps" is
> far clearer than "Dumps" in this case.
>
> > + (define page-header "Recent Events")
> > +
> > (layout
> > + #:title
> > + page-header
> > #:body
> > `(,(header)
> > (div
> > @@ -200,7 +208,7 @@
> > (@ (class "col-sm-12"))
> > (a (@ (href "/jobs"))
> > (h3 "Jobs"))
> > - (h1 "Recent events")))
> > + (h1 ,page-header)))
>
> The capitalisation used here "events" rather than "Events" is
> intentional, I wouldn't change it while looking at the titles at least.
>
> > (define (view-job job-id query-parameters log)
> > + (define page-header "Job")
> > +
> > (layout
> > + #:title
> > + (string-append page-header " " job-id)
> > #:body
> > `(,(header)
> > (div
> > @@ -339,7 +356,7 @@
> > (@ (class "row"))
> > (div
> > (@ (class "col-sm-12"))
> > - (h1 "Job " ,job-id)))
> > + (h1 ,page-header ," " ,job-id)))
>
> I'd be tempted to combine the Job string and the job-id then use it for
> both the #:title and h1 element.
>
> > + (string-append page-header " " (string-take commit-hash 7) " Channel News Entries")
>
> This title looks good, I'd put the more specific bits nearer the start
> though, so I'd put "Channel News Entries" first, then the Revision bit
> second. Also, watch out for the line length, I'd indent this so it's not
> longer than 80 lines.
next prev parent reply other threads:[~2021-04-16 9:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 9:01 [Outreachy] - Guix Data Service - Set a more informative page title Canan Talayhan
2021-04-13 11:57 ` Maxime Devos
2021-04-13 15:56 ` Canan Talayhan
2021-04-13 17:51 ` Maxime Devos
2021-04-15 12:08 ` Canan Talayhan
2021-04-15 21:52 ` Christopher Baines
2021-04-16 9:58 ` Canan Talayhan [this message]
2021-04-16 11:11 ` Christopher Baines
2021-04-18 13:42 ` Canan Talayhan
2021-04-18 17:53 ` Christopher Baines
2021-04-18 20:37 ` Canan Talayhan
2021-04-19 19:16 ` Christopher Baines
2021-04-21 15:43 ` Canan Talayhan
2021-04-22 19:46 ` Christopher Baines
2021-04-23 8:34 ` Canan Talayhan
2021-04-23 12:10 ` Christopher Baines
2021-04-24 11:39 ` Christopher Baines
2021-04-24 15:30 ` Canan Talayhan
2021-04-24 20:21 ` Christopher Baines
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='CAAosC5Ky5i=dCKjYvbDTA_4Uo6QvrW1ykRXCMkvXSG2JPR=kVg@mail.gmail.com' \
--to=canan.t.talayhan@gmail.com \
--cc=guix-devel@gnu.org \
--cc=mail@cbaines.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.