From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#26006: [Website] Integral update proposal Date: Tue, 07 Mar 2017 15:13:30 +0100 Message-ID: <87o9xdb2et.fsf@gnu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43475) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1clFsL-0001GR-6f for bug-guix@gnu.org; Tue, 07 Mar 2017 09:14:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1clFsH-00073S-WC for bug-guix@gnu.org; Tue, 07 Mar 2017 09:14:05 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:45557) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1clFsH-00073L-RW for bug-guix@gnu.org; Tue, 07 Mar 2017 09:14:01 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1clFsH-0001hT-KL for bug-guix@gnu.org; Tue, 07 Mar 2017 09:14:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: (sirgazil's message of "Mon, 06 Mar 2017 21:02:39 -0500") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: sirgazil Cc: 26006@debbugs.gnu.org Hello sirgazil! It=E2=80=99s always a pleasure to read you. :-) Basically, I like all of = your proposals. Some comments below. sirgazil skribis: > Navigation bar > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > Bar mockup: https://multimedialib.files.wordpress.com/2017/03/guixsd-menu= -2017-03-06.png > > The current navigation bar is growing, so I think it may be good to defin= e a style so that people can build more complex menus if necessary (but I h= ope it won't get too complex). > > I propose the graphic change you see in the mockup=E2=80=94thin black lin= e at the bottom, navigation items are white while idle, and yellow with a b= lack indicator at the bottom when active=E2=80=94 as well as the actual ite= ms and their ordering. Very good idea, definitely an improvement. > Home page > =3D=3D=3D=3D=3D=3D=3D=3D=3D > > Home mockup: https://multimedialib.files.wordpress.com/2017/03/guixsd-hom= e-view-2017-03-06.png > > I propose the changes in the mockup above because of the following reason= s: > > 1. Some people still confuse Guix with GuixSD. > 2. Some people still ask if Guix can be used on top of other distribution= s. > 3. Some people think pitching GuixSD and Guix to specific crowds is good = (of course it is). [1] > > To address the first two points, I changed the order of the content so th= at information refers to GuixSD first, Guix as a part of it, and then added= a section that mentions specifically the use of Guix in other distros. > > For point three, I added a section that links to blog posts that explain = GuixSD and Guix in the context of a particular field (this part requires th= e current News pages to become a Blog instead. See below). > > Finally, Ricardo Wurmus commented that there were too many styles of butt= ons, and I agree with him, so I made them homogeneous. Agreed. > News pages > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > News list mockup: https://multimedialib.files.wordpress.com/2017/03/guixs= d-blog-list-2017-03-06.png > News details mockup: https://multimedialib.files.wordpress.com/2017/03/gu= ixsd-blog-post-2017-03-06.png > > I suggest to convert News into a blog instead. This could make it easier = to add information targeted at different audiences without making the websi= te more complex. Additionally, we could move to the blog content like talks= , papers, and posts currently listed in the Help page. Sounds great. > I remember that Ludovic commented in #guix that he would like a better wa= y to display talks in the website... [2] With the design in the mockup abov= e, you just click on the "Talks" tag, and you have a nice preview and summa= ry of all talks. Yes! There=E2=80=99s also the question of how much work it=E2=80=99ll be t= o maintain the talks part (like whether we need to manually make =E2=80=9Cposters=E2= =80=9D for each video and so on.) The less work, the better. At the same time, we should reach out to people who=E2=80=99d like to contr= ibute to Guix in a less-technical way. There=E2=80=99s a lot that could be done = to keep the web site lively, and it would be great to let more people take care of that. > Also, Haunt, the current static site generator used to build the website,= can create an atom feed for every tag in the blog, so people can subscribe= to whatever topic is more interesting to them. Personally, I'd like to sub= scribe to a "Security" feed to keep informed about important security updat= es (see bug #25852). [3] I agree, we should use tags. A first step will be to add tags to the existing posts. > Packages pages > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > Package list mockup: https://multimedialib.files.wordpress.com/2017/03/gu= ixsd-package-list-2017-03-06.png > Package details mockup: https://multimedialib.files.wordpress.com/2017/03= /guixsd-package-detail-2017-03-06.png > > I actually proposed this update in bug #25227,[4] but decided to review t= he whole website design, so I put it here for reference. There=E2=80=99s still the issue that we don=E2=80=99t have screenshots, but= other than that it looks great. > Help page > =3D=3D=3D=3D=3D=3D=3D=3D=3D > > * Move talks, papers, and posts to the Blog. > * Allow little boxes to be distributed along the whole width of the scree= n. Good. > Contribute page > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > * Allow little boxes to be distributed along the whole width of the scree= n. > > > Infrastructure > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > Personally, I'd like to be able to access the website at "guixsd.org", an= d use a git repository for deployment of the static website. > > However, we are currently using the resources provided by Savannah for ho= sting, which means we have to use a CVS repository to deploy the website. A= s mentioned in bug #25227, using CVS could block the implementation of the = packages pages as shown in the mockups above (and maybe filtering blog post= s by tag) because CVS could choke on the thousands of pages that would be g= enerated (if we keep using a static website). > > To find a solution to this issue, Ludovic sent an email to Savannah admin= s asking for the possibility of using a dynamic website instead. I don't re= member if there was an answer. There was none. I don=E2=80=99t think we can get the level of support we=E2=80=99d like fro= m the gnu.org webmasters, who are already swamped. With Alex S. (Cc=E2=80=99d) and other= s at FOSDEM, we discussed this issue and concluded that we should consider moving the web site to infrastructure we control, where we could do things in any way we like. We won=E2=80=99t run a Libreboot-based physical machine for that because wi= th the current lack of IPMI support, we=E2=80=99d easily end up with downtimes unacceptable for a web site. However, we could use some sort of commercial hosting. I=E2=80=99m not much of a Web person so you and other Web-savvy people shou= ld consider themselves empowered to come up with a solution. :-) We have some funding that we could probably use for that. Thoughts? Thanks, Ludo=E2=80=99.