Re: [ART] Website mockup rev2

[Ludovic Courtès]

¡Hola!

Luis Felipe López Acevedo <address@hidden> skribis:

> Here is a revision of the last mockup for the website [1]. This time
> aimed at a techie audience.
>
> http://sirgazil.bitbucket.org/static/temp/img/guixsd/home-view-rev2.jpg

Very nice design again!

> Note that some sections that are currently available in
> <http://www.gnu.org/software/guix/> are not present in this mockup. I'm
> not suggesting to remove them, though. In the image I have of the future
> website, I think these sections could be located in appropriate pages.
> For example:
>
> - Status and Downloading. These could be in the Download page.
> - Getting involved. This would go in Contribute. And I'd suggest to use
> a simple layout such as the one used in the GNOME website
> <http://www.gnome.org/get-involved/>.
> - Maintainer and Licensing. These could be in the About page.
>
> What do you think?

Agreed on these points.

I have some more specific comments.

There’s some informal wording that I dislike; for instance, I would:

  - remove “We need skilled people”
  - change “Know the system...” to “Discover GuixSD”
  - change “Some screenshots...” to “Screenshots”
  - change “We have some news...” to “News”
  - change “Get in touch...” to “Contact” (?)
  - change “The devs are working hard...” to “Latest Development News”.

I would rather not have a Web interface to connect to the IRC channel.
The technical audience we’re targeting may know how to do that anyway.

Regarding the section at the bottom, I wonder whether/how it could be
implemented in practice.  For instance, we’re not going to move to
GitHub just for that, and I’d rather not call out to openhub.com or
similar to get stats.  Yet, I’m not sure the cgit/gitweb instances at
Savannah provide a JSON API to extract this kind of data.  What are your
thoughts on this?

Maybe the answer is that we’ll have to work with the Savannah hackers to
add whatever service provides such an API to Savannah, and in the
meantime live without that section.

One thing we need to decide is whether we keep the GuixSD web site
separate from gnu.org/s/guix.  I tend to think that it should be
separate (we can ask for guixsd.gnu.org), with the Guix web page mostly
unchanged, but I’m slightly concerned about overlap and the risk of
bitrot.  WDYT?

How can we make progress from here?  Would you be able to do the
CSS/HTML implementation of the web site?  What else is needed?

Thank you!

Ludo’.