unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: sirgazil <sirgazil@zoho.com>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: "\"Ludovic Courtès\"" <ludo@gnu.org>, Guix-devel <guix-devel@gnu.org>
Subject: Re: We need your feedback of the documentation videos!
Date: Tue, 22 Oct 2019 11:25:27 -0500	[thread overview]
Message-ID: <16df4499bf6.d6659b0f22661.6695205596769599213@zoho.com> (raw)
In-Reply-To: <20191022120504.7cyoc5x2exylpzrg@pelzflorian.localdomain>

Hi, Florian :)


---- On Tue, 22 Oct 2019 07:05:04 -0500 pelzflorian (Florian Pelz) <pelzflorian@pelzflorian.de> wrote ----

 > OAOn Sat, Oct 19, 2019 at 11:00:34PM +0200, pelzflorian (Florian Pelz) wrote: 
 > > On Sat, Oct 19, 2019 at 10:13:59PM +0200, Ludovic Courtès wrote: 
 > > > […] if you wanted to integrate them on 
 > > > the web site, I think that’d be great. 
 > > > 
 > > 
 > > I suppose the “Discover Guix” section on the homepage should advertise 
 > > Guix System and the videos, maybe in buttons next to the ALL PACKAGES 
 > > button.  I will look at making a proposal next week.  I am nowhere 
 > > near as creative as the website’s authors, so maybe others will think 
 > > of better designs. 
 > > 
 > > 
 >  
 > Do you have in mind something like the attached patch?  It does not 
 > yet add all of the videos; this is more proof of concept-like. 


I think that these changes and a blog post about the availability of these videos would work well to get the videos to the public as soon as possible.

The only thing I'd recommend against would be the yellow headers in the videos page because they don't satisfy the WCAG 2.0 level AA contrast requirements (one of my goals with the website design was to follow level AA guidelines at least).

Now, personally, if I had the time, I would have designed the videos page in a similar way to the blog page, and also done something like this:

* Add a "media" menu to the navbar with "screenshots" and "videos" items.
* Add a "media" app that would hold the definitions for videos and screenshots (the latter would move from the base app).
* Add a "tracks" field to the "video" record and a corresponding "track" record type for future subtitles.
* Add three video previews to the home page, below the screenshot previews, maybe using a heading like "Instructional videos".
* Add a new entry to the Help page, next to "GNU Guix Manual", with the same "Instructional videos" title.


 > > > Especially since we now host the web site by ourselves, we could also 
 > > > host the videos there, so that can be pretty easy to do. 
 > > > 
 > > > WDYT? 
 > > > 
 > > > Ludo’. 
 > > 
 > > I cannot judge whether audio-video.gnu.org is better or worse than 
 > > berlin. 
 > > 
 >  
 > Putting the video files in the guix-artwork git repository may be 
 > wrong, so the patch does not do that yet, instead still referencing 
 > archive.org which seems wrong too. 

Is there any ethical issue with using archive.org that I'm not aware of? I suggested Laura to upload videos there...

In any case, since it is already possible, it would be great to use Guix own hosting resources.

  reply	other threads:[~2019-10-22 16:25 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-16 15:11 We need your feedback of the documentation videos! Laura Lazzati
2019-07-16 17:40 ` pelzflorian (Florian Pelz)
2019-07-17  6:31 ` Dimakakos Dimos
2019-07-17  7:55   ` pelzflorian (Florian Pelz)
2019-07-30 14:37     ` pelzflorian (Florian Pelz)
2019-07-17  7:11 ` Tanguy Le Carrour
2019-07-17  9:44 ` Ricardo Wurmus
2019-07-30 13:26   ` Laura Lazzati
2019-07-30 15:03     ` Tobias Geerinckx-Rice
2019-07-30 17:12       ` Tobias Geerinckx-Rice
2019-07-30 14:06   ` pelzflorian (Florian Pelz)
2019-08-08 15:04   ` Laura Lazzati
2019-08-08 15:48     ` Ricardo Wurmus
2019-08-13 18:03       ` Laura Lazzati
2019-08-25 18:55         ` Laura Lazzati
2019-10-17  4:34           ` pelzflorian (Florian Pelz)
2019-10-19 20:13             ` Ludovic Courtès
2019-10-19 21:00               ` pelzflorian (Florian Pelz)
2019-10-22 12:05                 ` pelzflorian (Florian Pelz)
2019-10-22 16:25                   ` sirgazil [this message]
2019-10-22 18:59                     ` pelzflorian (Florian Pelz)
2019-10-23 11:49                       ` pelzflorian (Florian Pelz)
2019-10-23 14:33                         ` sirgazil
2019-10-25  6:35                       ` pelzflorian (Florian Pelz)
2019-10-25  8:12                         ` pelzflorian (Florian Pelz)
2019-10-25 14:25                           ` sirgazil
2019-10-25 20:32                         ` Ludovic Courtès
2019-10-25 21:58                           ` pelzflorian (Florian Pelz)
2019-10-26 14:29                             ` pelzflorian (Florian Pelz)
2019-10-27 19:47                               ` sirgazil
2019-10-28  7:41                                 ` pelzflorian (Florian Pelz)

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=16df4499bf6.d6659b0f22661.6695205596769599213@zoho.com \
    --to=sirgazil@zoho.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=pelzflorian@pelzflorian.de \
    /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).