unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
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 14:27:44 -0500	[thread overview]
Message-ID: <873861hfbj.fsf@netris.org> (raw)
In-Reply-To: <1424215729.3494.10.camel@openmailbox.org> ("Luis Felipe López Acevedo"'s message of "Tue, 17 Feb 2015 18:28:49 -0500")

Hi Luis,

Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> writes:
> Here is a revision of the last website mockup [1].
>
> White header
> http://sirgazil.bitbucket.org/static/temp/img/guixsd/home-view-white-rev1.png

The design is beautiful, but at this stage in our development, I think
it targets the wrong audience.  It will probably be at least a few years
before we can target the "Average Jane", and we shouldn't try anytime
soon.

For example, it would be a tremendous drain on us to draw a bunch of
people to our IRC channel who may not even be able to start their own
IRC client software.  At this stage, forcing users to run their own IRC
client is a helpful barrier to entry that we should not try to overcome
with an easy web interface.

Also, you have replaced "Dependendable, Hackable, and Liberating" with
"Libre, gratis, secure, and malleable".  I prefer the words we emphasize
on our current web page.  Ludovic has given several talks and had many
discussions with other GNU hackers, and settled on the words he chose,
and the language used to describe them, based on his experiences.  For
the audience we currently need to attract, I think that we should stick
with his language.

So, for now I think that our page should be aimed at skilled developers
and sysadmins, and so instead of headlining things like clip art of a
computer monitor, we should instead headline the unusual technical
features that we offer, with links to the best documentation, papers and
talks where they can find out more, and with information on how to get
involved without trying to lower the barriers to entry more than is
appropriate.

Does that make sense?

That said, our current web page could definitely use graphic redesign
and reorganization of its content, and I think you would be a great
person to help with that, if you can do so while retaining its technical
focus.

Thanks again for all of your help.  We are fortunate to have such a
talented artist helping :)

      Mark

  parent reply	other threads:[~2015-02-19 19:27 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
2015-02-19 19:27 ` Mark H Weaver [this message]
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=873861hfbj.fsf@netris.org \
    --to=mhw@netris.org \
    --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).