From: ludo@gnu.org (Ludovic Courtès)
To: David Thompson <dthompson2@worcester.edu>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] website: Convert implementation to SXML.
Date: Wed, 06 May 2015 21:09:31 +0200 [thread overview]
Message-ID: <87vbg5setw.fsf@gnu.org> (raw)
In-Reply-To: <87egmt4rfz.fsf@fsf.org> (David Thompson's message of "Wed, 06 May 2015 12:10:56 -0400")
David Thompson <dthompson2@worcester.edu> skribis:
> Mathieu Lirzin <mthl@openmailbox.org> writes:
>
>> This patch is a draft for the html->sxml website conversion.
>
> Looking good!
Indeed!
> But, I have one comment overall about our development strategy:
>
> I see a lot of absolute paths like
> '/software/guix/static/base/css/base.css'. These will of course work
> when viewing the site on gnu.org, but how do we develop the site on our
> own computers?
I was wondering too, does IceCat have a plug-in to specify the root of
such URLs?
> Ideally, I'd like to be able to generate the site and serve it with
> Guile's HTTP server to see what the result looks like before
> committing patches.
Sure. I think what Mathieu provides is a good first step, and I’ll
happily commit the wrapped-lines version if there are no objections.
The next step would be to introduce a (www utils) module, say. It would
have, among other things:
(define current-url-root
(make-parameter "/"))
(define (static-url-base)
(string-append (current-url-root) "/static/base"))
(define (css-url file)
(string-append (static-url-base) "/css"))
and so on. The pages would be modified to use these procedures instead
of hard-coded paths.
How does that sound?
Thanks, Mathieu!
Ludo’.
next prev parent reply other threads:[~2015-05-06 19:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 15:52 [PATCH] website: Convert implementation to SXML Mathieu Lirzin
2015-05-06 16:10 ` David Thompson
2015-05-06 19:09 ` Ludovic Courtès [this message]
2015-05-06 23:27 ` Mathieu Lirzin
2015-05-07 13:07 ` Ludovic Courtès
2015-05-07 13:59 ` Mathieu Lirzin
2015-05-06 16:15 ` David Thompson
2015-05-06 18:24 ` Luis Felipe López Acevedo
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=87vbg5setw.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=dthompson2@worcester.edu \
--cc=guix-devel@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).