From: "Luis Felipe López Acevedo" <felipe.lopez@openmailbox.org>
To: ludo@gnu.org
Cc: guix-devel@gnu.org
Subject: Re: Website development questions
Date: Sun, 20 Nov 2016 15:17:58 -0500 [thread overview]
Message-ID: <4c33f39cbd6c869e205ba58503e93bf4@openmailbox.org> (raw)
In-Reply-To: <877f85gj51.fsf@gnu.org>
On 2016-11-15 04:57, ludo@gnu.org wrote:
> Hello!
>
> Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:
>
>> I cloned the website to try a fix for bug #22115, and wanted to ask
>> first what process do you follow to try out the whole website locally?
>> When I build and serve the website with Haunt, I face the following
>> problems:
>>
>> 1. Pages don't load static files because they are looking for the
>> "static" directory in "/software/guix/static". Do I need to set some
>> variable first?
>
> To test locally, you need to do:
>
> $ GUIX_WEB_SITE_LOCAL=yes haunt build
> $ haunt serve
>
> There should be no broken links, except for links to the manual or
> other
> parts of gnu.org.
>
> I suppose this should go to README…
>
>> 2. The Packages and Packages Issues pages, which are defined in (www
>> packages) are commented out. How do you deal with those in
>> development?
>
> That’s on purpose, so that people don’t need to have Guix installed to
> hack on the web site.
>
> We build these pages separately using the ‘export-web-page’ procedure.
Ludo, I'm not sure how to do this part. Do I just import (www) and (www
packages) in a REPL, and call `export-web-page` for each page (packages
index and issues)? You don't have to modify `www.scm` at all (uncomment
elements in the %web-pages list, for example)?
Also, trying just that, when I try importing (www packages), (guix ui)
is not found in my system:
scheme@(guile-user)> (use-modules (www packages))
;;; compiling
/home/anonimo/Documentos/guix-artwork/website/www/packages.scm
;;; WARNING: compilation of
/home/anonimo/Documentos/guix-artwork/website/www/packages.scm failed:
;;; ERROR: no code for module (guix ui)
While compiling expression:
ERROR: no code for module (guix ui)
I'm using Guile 2.0.13 installed from Guix binary on Debian 8, and guix
is version 20161113.19. Where are Guix modules?
Thanks,
--
Luis Felipe López Acevedo
http://sirgazil.bitbucket.org/
next prev parent reply other threads:[~2016-11-20 20:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 18:15 Website development questions Luis Felipe López Acevedo
2016-11-15 9:57 ` Ludovic Courtès
2016-11-16 17:55 ` Luis Felipe López Acevedo
2016-11-20 20:17 ` Luis Felipe López Acevedo [this message]
2016-11-21 1:39 ` Luis Felipe López Acevedo
2016-11-21 14:01 ` Ludovic Courtès
2016-11-21 14:55 ` Luis Felipe López Acevedo
2016-11-22 22:52 ` Ludovic Courtès
2016-11-23 0:59 ` Luis Felipe López Acevedo
2016-11-23 22:11 ` Ludovic Courtès
2016-11-24 1:24 ` Luis Felipe López Acevedo
2016-11-26 17:37 ` Ludovic Courtès
2016-11-27 1:02 ` Luis Felipe López Acevedo
2016-11-27 1:27 ` Luis Felipe López Acevedo
2016-11-28 14:02 ` Ludovic Courtès
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=4c33f39cbd6c869e205ba58503e93bf4@openmailbox.org \
--to=felipe.lopez@openmailbox.org \
--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).