From mboxrd@z Thu Jan 1 00:00:00 1970 From: sirgazil Subject: Re: website: showcase or list videos and slides, sources of all talks Date: Fri, 22 Dec 2017 23:05:50 -0500 Message-ID: References: <20171218183932.4keww4qjan7tuyty@abyayala> <87lghzf5op.fsf@netris.org> <87ind24tej.fsf@gnu.org> <20171219161552.3egcv3vm3uj6gdoy@abyayala> <876091t4hb.fsf@gnu.org> <278bd58e-dd7f-b57b-4973-680a312f1916@zoho.com> <87bmir9kg3.fsf@gnu.org> <4a06c5cf-22d1-73e5-f15a-069919345dd4@zoho.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44191) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eSxLr-0004Xa-QV for guix-devel@gnu.org; Sat, 23 Dec 2017 22:53:28 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eSxLq-0007NS-4l for guix-devel@gnu.org; Sat, 23 Dec 2017 22:53:27 -0500 Received: from sender-pp-092.zoho.com ([135.84.80.237]:25453) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1eSxLp-0007MI-SX for guix-devel@gnu.org; Sat, 23 Dec 2017 22:53:26 -0500 In-Reply-To: <4a06c5cf-22d1-73e5-f15a-069919345dd4@zoho.com> Content-Language: en-US List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: =?UTF-8?Q?Ludovic_Court=c3=a8s?= Cc: guix-devel@gnu.org On 22/12/17 09:00, sirgazil wrote: > On 22/12/17 04:32, Ludovic Courtès wrote: >> Hello, >> >> sirgazil skribis: >> >>> On 20/12/17 17:32, Ludovic Courtès wrote: >>>> Hartmut Goebel 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