unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: "Luis Felipe López Acevedo" <felipe.lopez@openmailbox.org>
Cc: guix-devel@gnu.org
Subject: Re: [ART] Website mockup rev1
Date: Thu, 19 Feb 2015 20:11:20 +0100	[thread overview]
Message-ID: <20150219191120.GB18433@debian> (raw)
In-Reply-To: <1424215729.3494.10.camel@openmailbox.org>

Hello,

as we are getting used to now, this is really impressive work!

I think we should give some more thought (and I do not have answers ready to
these questions) on which information we want to emphasise. As Adam, I think
it might be a bit premature to start with a download button, as clearly we
are not in a state where people download, boot a life system, and go ahead.
Personally, I think we should start with documentation, so people know where
they are heading; unfortunately, I realise that this might fit very poorly
with the nice graphic design that is based on the download button. Maybe the
first item could be a short description at least, with a link to more
comprehensive documentation. Or this could be integrated into the catch lines
above the download button, with orange links to documentation?

Concerning screenshots, I am a bit doubtful; in the end, we look more or less
like any other GNU/Linux distribution, so maybe they could come a little
bit later?

News and chat are nice to have, as well as the latest git commits.
For the chat, we should also give the #guix channel name on freenode and not
only the webchat.

What is missing are the mailing lists and the bug tracker. I think both are
important points where we encourage people to participate, so there should
be buttons to subscribe, a link to the bug tracker, and a button (?) to
submit a bug (maybe using the "mailto"-pseudo-url). If you think it is
useful, these could also be dynamic contents (with the latest open mailing
list threads, or the latest closed bugs, or something like that).

Any more ideas or reactions?

Thanks again for all this amazing work,

Andreas

  parent reply	other threads:[~2015-02-19 19:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17 23:28 [ART] Website mockup rev1 Luis Felipe López Acevedo
2015-02-18 13:25 ` Bruno Félix Rezende Ribeiro
2015-02-19 13:53   ` Luis Felipe López Acevedo
2015-02-18 14:41 ` Amirouche Boubekki
2015-02-19 14:01   ` Luis Felipe López Acevedo
2015-02-18 20:05 ` Daniel Pimentel
2015-02-19 14:02   ` Luis Felipe López Acevedo
2015-02-19 19:11 ` Andreas Enge [this message]
2015-02-19 19:27 ` Mark H Weaver
2015-02-19 21:04   ` Luis Felipe López Acevedo

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=20150219191120.GB18433@debian \
    --to=andreas@enge.fr \
    --cc=felipe.lopez@openmailbox.org \
    --cc=guix-devel@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).