* [orgweb] Making the git repo URL more visible
@ 2021-10-01 1:40 Adam Porter
2021-10-01 15:01 ` Timothy
2021-10-02 5:01 ` Bastien
0 siblings, 2 replies; 9+ messages in thread
From: Adam Porter @ 2021-10-01 1:40 UTC (permalink / raw)
To: emacs-orgmode
[-- Attachment #1: Type: text/plain, Size: 610 bytes --]
Hi Bastien, Timothy, et al,
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:
[-- Attachment #2: screenshot --]
[-- Type: image/png, Size: 181122 bytes --]
[-- Attachment #3: Type: text/plain, Size: 142 bytes --]
Other FOSS projects's sites seem to make their source code repo links
very prominent; could Org's web site do that too? :)
--
Thanks,
Adam
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [orgweb] Making the git repo URL more visible
2021-10-01 1:40 [orgweb] Making the git repo URL more visible Adam Porter
@ 2021-10-01 15:01 ` Timothy
2021-10-02 7:58 ` Adam Porter
2021-10-02 5:01 ` Bastien
1 sibling, 1 reply; 9+ messages in thread
From: Timothy @ 2021-10-01 15:01 UTC (permalink / raw)
To: Adam Porter; +Cc: emacs-orgmode
[-- 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
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [orgweb] Making the git repo URL more visible
2021-10-01 1:40 [orgweb] Making the git repo URL more visible Adam Porter
2021-10-01 15:01 ` Timothy
@ 2021-10-02 5:01 ` Bastien
2021-10-02 5:49 ` Timothy
2021-10-02 7:54 ` Adam Porter
1 sibling, 2 replies; 9+ messages in thread
From: Bastien @ 2021-10-02 5:01 UTC (permalink / raw)
To: Adam Porter; +Cc: emacs-orgmode
Hi Adam,
Adam Porter <adam@alphapapa.net> writes:
> Other FOSS projects's sites seem to make their source code repo links
> very prominent; could Org's web site do that too? :)
Done, let me know if it's good enough.
I was missing this prominent link too!
Thanks for reporting this,
--
Bastien
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [orgweb] Making the git repo URL more visible
2021-10-02 5:01 ` Bastien
@ 2021-10-02 5:49 ` Timothy
2021-10-02 7:54 ` Adam Porter
1 sibling, 0 replies; 9+ messages in thread
From: Timothy @ 2021-10-02 5:49 UTC (permalink / raw)
To: emacs-orgmode
[-- Attachment #1: Type: text/plain, Size: 177 bytes --]
Hi Bastien,
> Done, let me know if it’s good enough.
Just 2c from me, I’d be tempted to have put that on the contribute page ¯\_(ツ)_/¯.
All the best,
Timothy
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [orgweb] Making the git repo URL more visible
2021-10-02 5:01 ` Bastien
2021-10-02 5:49 ` Timothy
@ 2021-10-02 7:54 ` Adam Porter
1 sibling, 0 replies; 9+ messages in thread
From: Adam Porter @ 2021-10-02 7:54 UTC (permalink / raw)
To: Bastien; +Cc: orgmode list
Hi Bastien,
On Sat, Oct 2, 2021 at 12:03 AM Bastien <bzg@gnu.org> wrote:
>
> Hi Adam,
>
> Adam Porter <adam@alphapapa.net> writes:
>
> > Other FOSS projects's sites seem to make their source code repo links
> > very prominent; could Org's web site do that too? :)
>
> Done, let me know if it's good enough.
>
> I was missing this prominent link too!
Thanks, I think it's great having the git repo URL front-and-center on
the home page of FOSS projects.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [orgweb] Making the git repo URL more visible
2021-10-01 15:01 ` Timothy
@ 2021-10-02 7:58 ` Adam Porter
2021-10-02 8:11 ` Timothy
0 siblings, 1 reply; 9+ messages in thread
From: Adam Porter @ 2021-10-02 7:58 UTC (permalink / raw)
To: Timothy; +Cc: orgmode list
Hi Timothy,
On Fri, Oct 1, 2021 at 10:10 AM Timothy <tecosaur@gmail.com> wrote:
>
> 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?
Maybe this is moot, since Bastien already added the link to the home
page, but anyway...
On the Contribute page, I'd be in favor of having some kind of
heading, like "Source Code," and listing the git URL in text for easy
copying (i.e. not hiding the URL behind a descriptive link). It'd
also be good to have a clickable link to view the repo on Savannah.
Also, on that page, while I'm glad to have Bastien's sponsorship links
there, the "GitHub" link with the GitHub icon might be expected to be
a link to the git source code, because that's a common way to link to
a git repo on other projects' sites. So it might be good to put them
under a heading, like "Sponsor Development".
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [orgweb] Making the git repo URL more visible
2021-10-02 7:58 ` Adam Porter
@ 2021-10-02 8:11 ` Timothy
2021-10-02 10:18 ` Adam Porter
0 siblings, 1 reply; 9+ messages in thread
From: Timothy @ 2021-10-02 8:11 UTC (permalink / raw)
To: Adam Porter; +Cc: orgmode list
[-- Attachment #1: Type: text/plain, Size: 1018 bytes --]
Hi Adam,
> Maybe this is moot, since Bastien already added the link to the home
> page, but anyway…
>
> On the Contribute page, I’d be in favor of having some kind of
> heading, like “Source Code,” and listing the git URL in text for easy
> copying (i.e. not hiding the URL behind a descriptive link). It’d
> also be good to have a clickable link to view the repo on Savannah.
>
> Also, on that page, while I’m glad to have Bastien’s sponsorship links
> there, the “GitHub” link with the GitHub icon might be expected to be
> a link to the git source code, because that’s a common way to link to
> a git repo on other projects’ sites. So it might be good to put them
> under a heading, like “Sponsor Development”.
I think a “Source Code” header could make sense, with a link to the cgit page,
git clone line, and maybe a sentence or on Savannah for the unfamiliar. Perhaps
we could like to the org-contrib and website repos as well there?
All the best,
Timothy
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [orgweb] Making the git repo URL more visible
2021-10-02 8:11 ` Timothy
@ 2021-10-02 10:18 ` Adam Porter
2021-10-02 10:33 ` Timothy
0 siblings, 1 reply; 9+ messages in thread
From: Adam Porter @ 2021-10-02 10:18 UTC (permalink / raw)
To: emacs-orgmode
Timothy <tecosaur@gmail.com> writes:
> I think a “Source Code” header could make sense, with a link to the cgit page,
> git clone line, and maybe a sentence or on Savannah for the unfamiliar. Perhaps
> we could like to the org-contrib and website repos as well there?
Sounds good to me.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [orgweb] Making the git repo URL more visible
2021-10-02 10:18 ` Adam Porter
@ 2021-10-02 10:33 ` Timothy
0 siblings, 0 replies; 9+ messages in thread
From: Timothy @ 2021-10-02 10:33 UTC (permalink / raw)
To: Adam Porter; +Cc: emacs-orgmode
[-- Attachment #1: Type: text/plain, Size: 110 bytes --]
Hi Adam,
> Sounds good to me.
Thanks :) it’s nice to get a second opinion.
All the best,
Timothy
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2021-10-02 10:34 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-10-01 1:40 [orgweb] Making the git repo URL more visible Adam Porter
2021-10-01 15:01 ` Timothy
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
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).