From: ludo@gnu.org (Ludovic Courtès)
To: sirgazil <sirgazil@zoho.com>
Cc: 26006@debbugs.gnu.org
Subject: bug#26006: [Website] Integral update proposal
Date: Thu, 15 Jun 2017 09:59:53 +0200 [thread overview]
Message-ID: <877f0d65qe.fsf@gnu.org> (raw)
In-Reply-To: <e3cfcfc6-1514-f37f-ceb5-f4bf9b6f8a4d@zoho.com> (sirgazil@zoho.com's message of "Wed, 14 Jun 2017 15:36:25 -0500")
Hello,
sirgazil <sirgazil@zoho.com> skribis:
> On 13/06/17 17:08, Ludovic Courtès wrote:
[...]
>> I found it a little bit confusing that talks and papers now appear as if
>> they were blog posts, but after all it’s probably better to have it this
>> way, especially since tags allow people to find them more easily I guess.
>>
>> The packages pages look better than what we have (minus the loss of the
>> JS code to display the build status ;-)).
>
> About the JS, I couldn't figured out exactly how it works, so that I
> could adapt it to the new page structure. Additionally, there is the
> problem that the JS looks for packages in the DOM by id, and package ids
> are not unique, which confuses me. Also, using duplicated id attributes
> is non-valid HTML.
The current code that generates the package pages intends to compute
unique anchor names for each package (see ‘packages->anchors’), and I
think it’s those IDs that the JS code uses, isn’t it?
>> I think there are a few little changes that were made in the current
>> site that were lost in the process. For example, on the front page, we
>> now have “DOWNLOAD v0.13.0” instead of “TEST v0.13.0”. I’ve also seen
>> that links to the package definitions at git.sv.gnu.org from the package
>> pages no longer include the commit. Anyway, these are really tiny
>> issues but we should pay attention to them when we migrate.
>
> I updated the download button.
>
> As for the commit in the links, I tried to add it, but couldn't. I
> implemented this website using the Guix API as a user (installing guix
> with guix), but it seems that the code to generate the commit part in
> the links requires that the guix in the GUILE_LOAD_PATH be a git
> repository, right? Since it uses "git describe" on "guix/config.scm".
Indeed, good point. I guess we could have a fallback case for when ‘git
describe’ fails.
On a more practical level, what would you like the workflow to be like
from there on? I would prefer hosting the source on gnu.org rather than
{bitbucket,gitlab,github}.com and I would also prefer Git over
Mercurial, but I don’t want to be a hindrance so I’m open to
discussions. :-)
Thanks!
Ludo’.
next prev parent reply other threads:[~2017-06-15 8:01 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 2:02 bug#26006: [Website] Integral update proposal sirgazil
2017-03-07 11:16 ` ng0
2017-03-07 12:53 ` Catonano
2017-03-07 14:13 ` Ludovic Courtès
2017-03-10 16:46 ` sirgazil
2017-03-10 21:05 ` Ludovic Courtès
2017-10-01 11:02 ` ng0
2017-10-02 7:50 ` Ludovic Courtès
2017-10-02 8:36 ` ng0
2017-10-02 9:10 ` Ludovic Courtès
2017-06-08 19:06 ` sirgazil
2017-06-13 22:08 ` Ludovic Courtès
2017-06-14 20:36 ` sirgazil
2017-06-15 7:59 ` Ludovic Courtès [this message]
2017-06-16 2:52 ` sirgazil
2017-06-16 7:05 ` Ludovic Courtès
2017-06-16 14:46 ` sirgazil
2017-06-17 4:57 ` Catonano
2017-06-17 7:16 ` Catonano
2017-06-17 15:46 ` sirgazil
2017-06-17 16:09 ` Catonano
2017-06-17 16:41 ` sirgazil
2017-06-17 17:12 ` Catonano
2017-06-17 18:11 ` sirgazil
2017-06-17 15:19 ` sirgazil
2017-06-17 15:19 ` Catonano
2017-07-29 17:53 ` Ludovic Courtès
2017-08-01 22:13 ` sirgazil
2017-12-06 17:10 ` bug#26006: New web site is on line! Ludovic Courtès
2017-12-06 17:55 ` Alex Sassmannshausen
2017-12-06 22:10 ` Adonay Felipe Nogueira
2017-12-06 22:10 ` Adonay Felipe Nogueira
2017-12-07 8:54 ` Ludovic Courtès
2017-12-07 3:01 ` sirgazil
2017-12-07 9:16 ` Chris Marusich
2017-12-07 17:10 ` pelzflorian (Florian Pelz)
2017-12-07 20:58 ` Ludovic Courtès
2017-12-08 18:42 ` Quiliro Ordonez Baca
2017-12-08 19:07 ` pelzflorian (Florian Pelz)
2017-07-01 14:26 ` bug#26006: [Website] Integral update proposal Ludovic Courtès
2017-07-04 20:00 ` sirgazil
2017-07-04 20:09 ` Catonano
2017-07-05 0:45 ` sirgazil
2017-07-04 21:24 ` Ludovic Courtès
2017-07-05 1:26 ` sirgazil
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=877f0d65qe.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=26006@debbugs.gnu.org \
--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 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.