From: Chris Marusich <cmmarusich@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: website: say what Guix is at the very top
Date: Sat, 27 Jan 2018 16:33:17 -0800 [thread overview]
Message-ID: <87fu6qbz5e.fsf@gmail.com> (raw)
In-Reply-To: <87h8rb1grv.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Wed, 24 Jan 2018 15:19:00 +0100")
[-- Attachment #1.1: Type: text/plain, Size: 2249 bytes --]
ludo@gnu.org (Ludovic Courtès) writes:
> Hello,
>
> Chris Marusich <cmmarusich@gmail.com> skribis:
>
>> Ricardo Wurmus <rekado@elephly.net> writes:
>>
>>> Hi Guix,
>>>
>>> on the website it starts right away with a list of features:
>>> “Liberating”, “Dependable”, and “Hackable”. But what is this thing
>>> called Guix?
>>>
>>> We should add a very short paragraph above that list to say what Guix
>>> and GuixSD are.
>>>
>>> What do you think?
>>
>> How is Guix different from other package managers? Why is it better?
>
> That’s what Liberating (free software), Dependable (transactional,
> etc.), Hackable (it’s a Scheme API) tries to convey.
>
> The hope was that by reading these 3 items people could tell how it
> differs from APT/dpkg, Conda, or Nix.
To be honest, I really like the current list of 3 items. I think it's a
good "marketing" front page, even if perhaps it doesn't provide a
complete answer of what Guix is. What do you think about making these
minor changes to the website (see attached).
>> Perhaps the best way to do that would be to write a problem statement.
>> Instead of explaining what Guix is, explain what problems Guix solves.
>> The first chapter of Eelco Dolstra's Ph. D. thesis [1] did a fantastic
>> job of explaining what problems Nix solves, and by the end of that
>> chapter, I was really excited to learn more about Nix (and Guix) and try
>> it out. In particular, the list of problems with the state of the art
>> in section 1.3 "Motivation" and the list of solutions that Nix offers in
>> section 1.5 "Contributions" were particularly concise and convincing.
>> Maybe we can aim for something similar on our Guix website?
>
> The “Introduction” and “Features” sections of the manual aim to achieve
> that goal, but in a “constructive” way (stating what properties it has,
> rather than what properties other solutions lack.) However, I think
> it’s not that concise and it’s quite technical, so I’d keep that in the
> manual rather than on the front page.
>
> Thoughts?
I agree. Our manual is great overall. If I can think of ways to
improve it even more, I'll submit more patches for review.
--
Chris
[-- Attachment #1.2: 0001-website-Clarify-the-descriptions-of-Guix-and-GuixSD.patch --]
[-- Type: text/x-patch, Size: 2971 bytes --]
From adf588a9daa73072ad3f1b39581ba5881a6cf780 Mon Sep 17 00:00:00 2001
From: Chris Marusich <cmmarusich@gmail.com>
Date: Sat, 27 Jan 2018 16:31:02 -0800
Subject: [PATCH] website: Clarify the descriptions of Guix and GuixSD.
* website/apps/base/templates/home.scm: Clarify descriptions.
---
website/apps/base/templates/home.scm | 47 +++++++++++++++++++++---------------
1 file changed, 27 insertions(+), 20 deletions(-)
diff --git a/website/apps/base/templates/home.scm b/website/apps/base/templates/home.scm
index f7c2d1c..beb1b39 100644
--- a/website/apps/base/templates/home.scm
+++ b/website/apps/base/templates/home.scm
@@ -36,10 +36,27 @@
(@ (class "featured-content"))
(h2 (@ (class "a11y-offset")) "Summary")
(ul
+ (li
+ (b "Dependable.")
+ ,(link-yellow
+ #:label "GNU Guix"
+ #:url (manual-url "Package-Management.html"))
+ " is a "
+ ,(link-yellow
+ #:label "purely functional"
+ #:url (manual-url "Introduction.html#index-functional-package-management"))
+ " package management tool. In addition to standard package
+ management features, it supports transactional upgrades
+ and roll-backs, unprivileged package management, per-user profiles, "
+ ,(link-yellow
+ #:label "and more"
+ #:url (manual-url "Features.html"))
+ ".")
+
(li
(b "Liberating.")
- " The Guix System Distribution (GuixSD) is an advanced
- distribution of the "
+ " The GNU Guix System Distribution (GuixSD) is an advanced
+ distribution of the "
,(link-yellow
#:label "GNU operating system"
#:url (gnu-url "gnu/about-gnu.html"))
@@ -47,34 +64,24 @@
,(link-yellow
#:label "GNU Project"
#:url (gnu-url))
- "—which respects the "
+ ", with Guix at its core. Because GuixSD is "
,(link-yellow
- #:label "freedom of computer users"
+ #:label "FSDG"
#:url (gnu-url "distros/free-system-distribution-guidelines.html"))
- ". ")
-
- (li
- (b "Dependable.")
- " It comes with the "
- ,(link-yellow
- #:label "GNU Guix package manager"
- #:url (manual-url "Package-Management.html"))
- ", which in addition to standard package management features,
- supports transactional upgrades and roll-backs, unprivileged
- package management, per-user profiles, "
+ "-compliant, all software in the distribution"
,(link-yellow
- #:label "and more"
- #:url (manual-url "Features.html"))
- ".")
+ #:label "respects your freedom"
+ #:url (gnu-url "philosophy/free-sw.html"))
+ ". ")
(li
(b "Hackable.")
- " It provides "
+ " Both Guix and GuixSD provide "
,(link-yellow
#:label "Guile Scheme"
#:url (gnu-url "software/guile/"))
" APIs, including high-level embedded domain-specific
- languages (EDSLs) to "
+ languages (EDSLs) to declaratively "
,(link-yellow
#:label "define packages"
#:url (manual-url "Defining-Packages.html"))
--
2.15.1
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-01-28 0:33 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
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 [this message]
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=87fu6qbz5e.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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).