From: sirgazil <sirgazil@zoho.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: website: showcase or list videos and slides, sources of all talks
Date: Fri, 22 Dec 2017 23:05:50 -0500 [thread overview]
Message-ID: <f98db4ca-618a-98b8-2975-08670fda3bf6@zoho.com> (raw)
In-Reply-To: <4a06c5cf-22d1-73e5-f15a-069919345dd4@zoho.com>
On 22/12/17 09:00, sirgazil wrote:
> On 22/12/17 04:32, Ludovic Courtès wrote:
>> Hello,
>>
>> sirgazil <sirgazil@zoho.com> skribis:
>>
>>> On 20/12/17 17:32, Ludovic Courtès wrote:
>>>> Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:
>>>>
>>>>> Am 19.12.2017 um 17:15 schrieb ng0:
>>>>>>> It should be here:
>>>>>>>
>>>>>>> https://www.gnu.org/software/guix/blog/tags/talks/
>>>>>>> https://www.gnu.org/software/guix/blog/tags/papers/
>>>>>> This doesn't work really well to discover them, like on
>>>>>> a submenu page in the head menu, leading to these pages
>>>>>> or dedicated (non-blog, non-markdown) pages.
>>>>>>
>>>>> +1 for linking them from a more prominent page on the main website.
>>>>>
>>>>> Blogs are like a diary, but not good for documentation an important
>>>>> content.
>>>>
>>>> sirgazil, WDYT? :-)
>>>
>>> Well, I think we could convert the current Blog item in the website
>>> menu into a Media item with the following subitems:
>>>
>>> Blog
>>> Papers
>>> Screenshots
>>> Talks
>>
>> I like it; perhaps I’d leave “Blog” as a separate menu item though.
>
>
> I'm fine with that too.
>
>
>>> Just like screenshots and blog posts, some talks could be highlighted
>>> in the home page. These changes could make it easier for people to
>>> find them, I think.
>>
>> Could be nice.
>>
>>> We can design the new pages and update current pages so that people
>>> browsing the summaries of posts, talks, etc. know if the full content
>>> of a given item contains video, slides, etc.
>>>
>>> With these changes, which I think I can start designing right now, I
>>> think it would not be necessary to list talks and papers in the Help
>>> section again. What do you think, Mark?
>>
>> I prefer the idea of a “Media” menu, but perhaps you’re suggesting to do
>> both? That would be great.
Just read a comment from ng0 on #guix.¹ So, to be clear, going with the
"Media" idea would mean:
1. Adding the new "Media" menu.
2. Adding a "media" app with new data types for talks and papers, their
respective instances, and two new pages: Talks and Papers. The
screenshots page already exists.
The idea is not to create visible links to the existing blog posts that
contain talks and papers.
> Yes, I mean that we can have the "Media" menu, but we can also use, for
> example, the concept of post types in the blog (using post metadata), so
> that posts of types "video" or "slides" can have summaries that tell
> people that the post is a video or a slideshow.
Now, the use of types for blog posts would be just an additional change
that could make it easier for people to tell which posts have audio,
video or any other important media. Since "it was easy to see at
a glance on the old site which talks included videos", I think the same
could apply to the previews of blog posts that include videos or other
multimedia content.
1. https://gnunet.org/bot/log/guix/2017-12-22#T1585025
next prev parent reply other threads:[~2017-12-24 3:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 18:39 website: showcase or list videos and slides, sources of all talks ng0
2017-12-19 9:05 ` Mark H Weaver
2017-12-19 15:41 ` Ludovic Courtès
2017-12-19 16:15 ` ng0
2017-12-20 16:02 ` Hartmut Goebel
2017-12-20 22:32 ` Ludovic Courtès
2017-12-21 18:58 ` sirgazil
2017-12-22 9:32 ` Ludovic Courtès
2017-12-22 14:00 ` sirgazil
2017-12-23 4:05 ` sirgazil [this message]
2017-12-19 21:04 ` Mark H Weaver
2018-01-04 20:15 ` Mark H Weaver
2018-01-08 10:58 ` Ludovic Courtès
2017-12-20 16:33 ` Tobias Geerinckx-Rice
2017-12-20 22:34 ` 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
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=f98db4ca-618a-98b8-2975-08670fda3bf6@zoho.com \
--to=sirgazil@zoho.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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).