all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Luis Felipe via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "47312@debbugs.gnu.org" <47312@debbugs.gnu.org>
Subject: bug#47312: [website] Showing channel news
Date: Mon, 22 Mar 2021 17:38:25 +0000	[thread overview]
Message-ID: <mIrUPMnuROYasH3o_wb4csFIx5NhBWZMORnuis269uAxZBmhBs4ezuq4wP4DdoSUL5jfNxgF576qlJl_snimIQ3_ziLDAWQyYTScUf4SArA=@protonmail.com> (raw)
In-Reply-To: <87sg4nzk52.fsf@gnu.org>

Hi, Ludo,

On Monday, March 22, 2021 8:07 AM, Ludovic Courtès <ludo@gnu.org> wrote:

> Hello!
>
> I figured it would be nice to display channel news (as shown by ‘guix
> pull --news’) on the web site. Perhaps the three latest items could be
> shown on the front page, as is done for blog posts, and then each entry
> would get its own page, similar to the layout of blog posts.

Where would these new pages live? Maybe:

List of News: /LANG_TAG/news/
News entry: /LANG_TAG/news/NEWS_ENTRY_COMMIT_VALUE/SLUGIFIED_ENTRY_TITLE/


> (guix channels) has ‘read-channel-news’ to read the news, the web site
> has code to render the blog posts, but I’m not sure how to adapt it to
> render news entries. Thoughts?

I'd like to help with this, but after helping with https://issues.guix.gnu.org/43871. Maybe what is found to work to generalize presentation of different media items in #43871 can be used for presenting channel news.

(I'm actually doing some related experimentation in my website)






  reply	other threads:[~2021-03-22 17:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-22  8:07 bug#47312: [website] Showing channel news Ludovic Courtès
2021-03-22 17:38 ` Luis Felipe via Bug reports for GNU Guix [this message]
2021-03-23 10:37   ` Ludovic Courtès

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='mIrUPMnuROYasH3o_wb4csFIx5NhBWZMORnuis269uAxZBmhBs4ezuq4wP4DdoSUL5jfNxgF576qlJl_snimIQ3_ziLDAWQyYTScUf4SArA=@protonmail.com' \
    --to=bug-guix@gnu.org \
    --cc=47312@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --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.