From: ludo@gnu.org (Ludovic Courtès)
To: "Luis Felipe López Acevedo" <felipe.lopez@openmailbox.org>
Cc: 25227@debbugs.gnu.org
Subject: bug#25227: [Website] Package-related pages redesign proposal
Date: Mon, 19 Dec 2016 22:14:58 +0100 [thread overview]
Message-ID: <87k2av1uzx.fsf@gnu.org> (raw)
In-Reply-To: <1ea95ccf0ed7cece5a04ded029944c98@openmailbox.org> ("Luis Felipe López Acevedo"'s message of "Mon, 19 Dec 2016 15:08:44 -0500")
Hello!
Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:
> On 2016-12-19 02:35, Alex Sassmannshausen wrote:
>> Hi Luis,
>>
>> Luis Felipe López Acevedo writes:
>>
>>> Hi,
>>>
>>> I was thinking on improving the package-related pages, and made these
>>> mockups:
>>>
>>>
>>> Figure 1. Package list page.
>>> https://multimedialib.files.wordpress.com/2016/12/guixsd-package-list-view-v0.png
Awesome, I really like both mockups!
>> Previous discussions centered around how difficult it is to maintain
>> categories for packages. I think if we went this way we'd want to
>> implement some form of deductive faceting, where we parse
>> description/synopsis and try to generate keywords. But that sounds
>> like
>> it could quite easily become a can of worms…
>
>
> If that is not possible, we can just ignore it for now :)
We already have categories for GNU packages, and in theory it might be
possible to get categories for non-GNU packages from the FSD
(directory.fsf.org).
But that’s just theory, so yes, probably best to keep it as future
work. :-)
In the meantime, we can try to find Someone willing to see how we could
get data from the FSD.
> Seeing the way the current logos from GNU packages are handled, I'm
> not optimist about having logos for non-GNU packages and screenshots
> for applications, any time soon. Too much manual work indeed. So I
> think we can ignore images, to keep it simple.
Agreed.
In the future, we could also try to get logos and screenshot from some
other database: FSD, Debian/Ubuntu, WikiData, etc.
> So I see that some parts of the design could be used in the current
> static site, advanced filtering and search may have to wait for a
> dynamic site, logos and screenshots may be a can of worms.
I’ve started a discussion with the Savannah folks (Cc’d you) to see
whether/how we could have those pages generated on the server side.
Thank you for the great work!
Ludo’.
next prev parent reply other threads:[~2016-12-19 21:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 3:12 bug#25227: [Website] Package-related pages redesign proposal Luis Felipe López Acevedo
2016-12-19 7:35 ` Alex Sassmannshausen
2016-12-19 20:08 ` Luis Felipe López Acevedo
2016-12-19 21:14 ` Ludovic Courtès [this message]
2019-02-12 16:57 ` sirgazil
2019-02-13 14:28 ` sirgazil
2020-09-27 16:54 ` sirgazil via Bug reports for GNU Guix
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=87k2av1uzx.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=25227@debbugs.gnu.org \
--cc=felipe.lopez@openmailbox.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 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).