unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, George myglc2 Clemmer <myglc2@gmail.com>,
	sirgazil <lizagris@protonmail.com>
Subject: Re: website: say what Guix is at the very top
Date: Sun, 21 Jan 2018 15:47:27 +0100	[thread overview]
Message-ID: <87r2qj1d6o.fsf@elephly.net> (raw)
In-Reply-To: <87r2qm3rfv.fsf@gnu.org>


Ludovic Courtès <ludo@gnu.org> writes:

> Ricardo Wurmus <rekado@elephly.net> skribis:
>
>> It seems unfortunate to me that we have one shared website for GuixSD
>> and Guix.  As much as I love GuixSD, I think Guix is the main “product”
>> and GuixSD would need to be moved to a subsite.  That’s primarily
>> because GuixSD can be explained in terms of Guix, but explaining Guix as
>> “the package manager we use for GuixSD” seems less helpful.
[…]
>> My proposal is to keep https://gnu.org/s/guix focussed on Guix the
>> functional software environment manager, and have the distro under
>> https://gnu.org/s/guix/distro.
>>
>> What do you think?
>
> In principle I think it’s a good idea.  In practice I’m not sure what
> this would look like, though.
>
> For instance, does that mean /distro would be a “second home page”, with
> screenshots, contacts, blog entries, baseline, and all?  Or would it be
> different?  What would be remove from or add to the actual home page?

I think of /distro as just a leaf page, not a whole website on its own.

- The logo in the menu bar should be the Guix logo.  The GuixSD logo
  could be shown in the contents of the /distro page.

- The menu should probably have an item for GuixSD

- The screenshots are applicable to GuixSD only, in my opinion, so they
  don’t make much sense on the Guix home page.  I guess we could have
  Guix-only text “screenshots” to show the command-line user interface.

- I’d remove the “All packages” button from “Discover GuixSD”

- “GNU Guix in other GNU/Linux distros” is a great section that should
  link to the Guix package manager’s home page.

- I would remove the blog, contact, and “GuixSD and GNU Guix in your
  field” sections from the distro sub-page to avoid duplication.

- The two sites should have separate Download sections.

… and as I imagine these changes I become confused about how to link to
these two download pages.  Having a single “Download” link at the top
bar would not work when we want to offer separate pages for GuixSD and
Guix.  We could have /distro/download, which would be linked from the
/distro page, just like we currently have /download linked from right
after the introduction.  It would have to be a very prominent button,
shown “above the page fold” so that we can drop the “Download” item
from the menu bar.

The download page for GuixSD should offer the GuixSD options first and
link to the Guix download page ater the options — and vice versa.

(I’m not as sure about these proposed individual changes as I am about
the proposal to separate the pages for Guix and GuixSD.)

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

  parent reply	other threads:[~2018-01-21 14:47 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-17 17:30 website: say what Guix is at the very top Ricardo Wurmus
2018-01-17 18:08 ` Tobias Geerinckx-Rice
2018-01-19  8:04   ` Ricardo Wurmus
2018-01-21 17:11     ` Tobias Geerinckx-Rice
2018-01-19  6:09 ` George myglc2 Clemmer
2018-01-19  7:42   ` Ricardo Wurmus
2018-01-19 13:32     ` Ludovic Courtès
2018-01-19 20:35       ` myglc2
2018-01-21 14:47       ` Ricardo Wurmus [this message]
2018-01-24  5:54         ` myglc2
2018-01-24 14:24           ` Oleg Pykhalov
2018-01-24 14:22         ` Ludovic Courtès
2018-01-26 23:03           ` myglc2
2018-01-27 16:14             ` Ludovic Courtès
2018-01-27 18:20               ` myglc2
2018-01-27 21:59                 ` Pjotr Prins
2018-01-28 16:24                 ` Ricardo Wurmus
2018-01-29  4:14                   ` myglc2
2018-01-29  7:37                     ` Pjotr Prins
2018-01-29 21:31                       ` Cook, Malcolm
2018-01-29 22:20                         ` Ricardo Wurmus
2018-01-29 22:24                           ` Cook, Malcolm
2018-01-30  1:03                             ` Ricardo Wurmus
2018-01-30 22:17                               ` myglc2
2018-01-30  1:43                             ` George myglc2 Clemmer
2018-01-30  2:56                               ` Ricardo Wurmus
2018-01-30  7:31                           ` Pjotr Prins
2018-01-30  7:46                           ` Pjotr Prins
2018-01-31 16:58                       ` myglc2
2018-01-31 17:27                         ` Pjotr Prins
2018-01-31 18:11                           ` myglc2
2018-01-31 18:13                             ` Pjotr Prins
2018-01-28  0:35               ` Chris Marusich
2018-01-22  7:04 ` Chris Marusich
2018-01-22 16:43   ` myglc2
2018-03-16  7:14     ` Pjotr Prins
2018-01-24 14:19   ` Ludovic Courtès
2018-01-28  0:33     ` Chris Marusich
2018-01-28 21:58       ` Ludovic Courtès
2018-01-29  2:08         ` Chris Marusich

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=87r2qj1d6o.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=lizagris@protonmail.com \
    --cc=ludo@gnu.org \
    --cc=myglc2@gmail.com \
    /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).