all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Timothy <tecosaur@gmail.com>
To: Adam Porter <adam@alphapapa.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [orgweb] Making the git repo URL more visible
Date: Fri, 01 Oct 2021 23:01:27 +0800	[thread overview]
Message-ID: <874ka0kch2.fsf@gmail.com> (raw)
In-Reply-To: <87zgrtplnx.fsf@alphapapa.net>

[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]

Hi Adam,

> Just now I found myself needing to look up the URL of the Org git repo,
> and it seemed a bit harder than it ought to be.  It’d be nice if there
> were a prominent “source code” link on the front page, but I remembered
> that it was somewhere on the “Contribute” page, so I opened that.

> When it loaded, I still overlooked the URL to the git repo.  I was
> expecting to see some kind of “Source Code” header, or “git repo” link,
> but instead the link is “The Org Codebase”, and it’s not under a header
> or near any other text like “source code” or “git repo”, so it seems
> easy to overlook:

Thanks for bringing this up. I agree that it should be more prominent. My
instinctual response is to change the text, add an icon, and bump the font size
up. Perhaps make it a /button link/ like “Tools that work with Org” on the
homepage. I’d be tempted to put it on the homepage, but I’m also wary of
clutter, and I’m hoping that the use of the common Git branch icon may clue devs
into thinking that the repository is linked/given on that page.

Do you have any thoughts on that?

All the best,
Timothy

  reply	other threads:[~2021-10-01 15:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-01  1:40 [orgweb] Making the git repo URL more visible Adam Porter
2021-10-01 15:01 ` Timothy [this message]
2021-10-02  7:58   ` Adam Porter
2021-10-02  8:11     ` Timothy
2021-10-02 10:18       ` Adam Porter
2021-10-02 10:33         ` Timothy
2021-10-02  5:01 ` Bastien
2021-10-02  5:49   ` Timothy
2021-10-02  7:54   ` Adam Porter

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=874ka0kch2.fsf@gmail.com \
    --to=tecosaur@gmail.com \
    --cc=adam@alphapapa.net \
    --cc=emacs-orgmode@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.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.