From: "Jérémy Korwin-Zmijowski" <jeremy@korwin-zmijowski.fr>
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Cc: Guix Help <help-guix@gnu.org>
Subject: Re: My Guile Hacker Handbook
Date: Thu, 23 Jul 2020 11:17:27 +0200 [thread overview]
Message-ID: <d5655041ac6892d593d35997499d835bce9d9930.camel@korwin-zmijowski.fr> (raw)
In-Reply-To: <fd5010a8-b2b9-b6eb-be81-f3f33384fc8c@posteo.de>
Hi Zelphir !
> The handbook looks great visually. I like the artwork, which is also
> used on the Guile website. It looks inviting to get going with
> coding.
The artwork used is not meant to stay as is but it does the job right
now. (Sirgazil, hope you don't mind...)
I have to custom the code highlight to handle scheme (default don't...)
> As for the website itself, how did you create it on the backend side?
> Ah
> I just saw the link to the repo!
I use a fork of mdbook to provide multi-language feature :
https://github.com/gambhiro/mdBook/tree/multilang/
(To share my vision, I would go for a Skribilo version some day)
> Default language seems to be French, which is fine. Might however
> lead
> to people missing the language switcher, if they do not understand
> French. Although it is at the top, so it should be pretty obvious.
> Perhaps an initial language chooser would be best.
I guess I will make english the default. And put some word about other
languages in the homepage.
> I also like the emphasis on testing in the guide.
It's my favorite too hahahaha
> Looking forward to any further content!
For sure, I think the awesome list you initiate will help to speed up
the process ! ;)
Thank you for your feedback ! It helps !
Jérémy
next prev parent reply other threads:[~2020-07-23 9:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 6:18 My Guile Hacker Handbook Jérémy Korwin-Zmijowski
2020-07-23 6:46 ` test anything? (Re: My Guile Hacker Handbook) Marc Chantreux
2020-07-23 15:08 ` a French mailing list (was: test anything? (Re: My Guile Hacker Handbook)) Dmitry Alexandrov
2020-07-23 20:34 ` Marc Chantreux
2020-07-23 7:41 ` My Guile Hacker Handbook Zelphir Kaltstahl
2020-07-23 9:17 ` Jérémy Korwin-Zmijowski [this message]
2020-07-23 10:32 ` Bonface M. K.
2020-07-23 14:09 ` Jérémy Korwin-Zmijowski
2020-07-24 0:58 ` Bonface M. K.
2020-07-24 0:06 ` No Guile on Windows? (was: My Guile Hacker Handbook) Dmitry Alexandrov
2020-07-24 5:41 ` Eli Zaretskii
2020-07-24 7:22 ` Dr. Arne Babenhauserheide
2020-07-24 9:32 ` Christopher Lam
2020-07-24 11:50 ` Mike Gran
2020-07-24 16:25 ` Licensing of Cygwin comatibility layer (was: No Guile on Windows?) Dmitry Alexandrov
2020-07-24 23:33 ` Mike Gran
[not found] ` <878sf9812f.fsf@gnu.org>
2020-07-24 14:20 ` No Guile on Windows? Stefan Israelsson Tampe
2020-07-24 17:46 ` Dr. Arne Babenhauserheide
2020-07-24 17:47 ` Dmitry Alexandrov
2020-07-24 18:41 ` Jan Wielkiewicz
2020-07-25 3:48 ` No Guile on Windows? (was: My Guile Hacker Handbook) David Pirotte
2020-07-25 6:31 ` Eli Zaretskii
2020-07-25 13:56 ` Christopher Lam
2020-07-25 14:28 ` Eli Zaretskii
2020-07-28 2:52 ` Christopher Lam
2020-07-25 16:49 ` Mike Gran
2020-07-25 16:33 ` Jérémy Korwin-Zmijowski
2020-07-25 21:38 ` No Guile on Windows? Dmitry Alexandrov
2020-07-24 6:47 ` No Guile on Windows? (was: My Guile Hacker Handbook) divoplade
2020-07-24 11:38 ` Stefan Israelsson Tampe
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=d5655041ac6892d593d35997499d835bce9d9930.camel@korwin-zmijowski.fr \
--to=jeremy@korwin-zmijowski.fr \
--cc=help-guix@gnu.org \
--cc=zelphirkaltstahl@posteo.de \
/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.
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).