From: "Ludovic Courtès" <ludo@gnu.org>
To: Luis Felipe <luis.felipe.la@protonmail.com>
Cc: Julien Lepiller <julien@lepiller.eu>,
"43871@debbugs.gnu.org" <43871@debbugs.gnu.org>
Subject: [bug#43871] [PATCH website] Add community page
Date: Tue, 13 Oct 2020 22:06:51 +0200 [thread overview]
Message-ID: <87y2k9hov8.fsf@gnu.org> (raw)
In-Reply-To: <q1zs49KModf58A5fGfRcemgcOdE87-D20jZt3lBRQmJ52htHXfk3gz3AhjzGQDsmzamOoQxIU6_5pf8MtFTePDPH-rxlynmd071bupoTc3E=@protonmail.com> (Luis Felipe's message of "Tue, 13 Oct 2020 12:47:11 +0000")
Hi,
Luis Felipe <luis.felipe.la@protonmail.com> skribis:
> Well, my idea was to have these kinds of resources grouped according to their types (https://lists.gnu.org/archive/html/guix-devel/2017-12/msg00356.html). So, instead of a Community resources entry in the Media menu, there would be separate entries like Talks, Papers, etc.
>
> So the Media part of the website could work like the Blog in that you could explore all kinds of media (/lang/media/) or media of some type (e.g. /lang/media/talks/).
Interesting, that makes sense to me, thanks for the reminder!
And yes, there’s already “Videos” and “Screenshots” (without /media in
the URL though), so I guess we could add “Talks” and “Papers” similarly.
Julien, does that look like a reasonable change to make? WDYT?
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-10-13 20:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 22:38 [bug#43871] [PATCH website] Add community page Julien Lepiller
2020-10-08 23:16 ` zimoun
2020-10-12 16:41 ` Ludovic Courtès
2020-10-12 19:45 ` Brett Gilio
2020-10-13 12:47 ` Luis Felipe via Guix-patches via
2020-10-13 20:06 ` Ludovic Courtès [this message]
2020-10-13 20:46 ` Julien Lepiller
2020-11-04 10:38 ` zimoun
2020-11-04 16:12 ` Luis Felipe via Guix-patches via
2020-11-04 18:31 ` zimoun
2020-11-05 0:36 ` Luis Felipe via Guix-patches via
2021-05-25 14:55 ` Luis Felipe via Guix-patches via
2021-05-25 15:07 ` Julien Lepiller
2021-07-01 13:31 ` Luis Felipe via Guix-patches via
2021-11-19 14:36 ` bug#43871: " Julien Lepiller
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=87y2k9hov8.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=43871@debbugs.gnu.org \
--cc=julien@lepiller.eu \
--cc=luis.felipe.la@protonmail.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.