unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Blake Shaw <blake@sweatshoppe.org>
To: Luis Felipe <luis.felipe.la@protonmail.com>
Cc: guile-user@gnu.org, Guix Devel <guix-devel@gnu.org>
Subject: Wiki && Re: [feature request] merge sxml->html from (haunt html) into guile?
Date: Wed, 29 Jun 2022 01:34:46 +0700	[thread overview]
Message-ID: <CAKjmbcDH8S90FW+xwo7XppU9G=qhTcYJUDPzU2Z9XHAHqLX87g@mail.gmail.com> (raw)
In-Reply-To: <skHXeytJhh-XZOWnqaD3Qi1z6uaXri9bDjPfcSBLVCZWzpsrNHqQ_aKLFiKN9Hhd4T2Ftu8Fqk_P6R7sHcZ5kqnfrr6L3Xk7SBDBYar09f8=@protonmail.com>

[-- Attachment #1: Type: text/plain, Size: 1977 bytes --]

Hi Luis,

(copying in Guix as I digress into the subject of a Wiki for Guix & Guile
communities)

Thanks for this! It's cool and I would not have found it without your help.

Which brings up another thing I've been considering working on thats been
discussed in the Guix community: the need for click-to-edit wiki, written
in Guile.

If we had a wiki up, there could be an "HTML" stub, for instance, that
collects links to all projects using HTML in guile. Finding out whats
available would be streamlined, and relatively painless to update and
moderate.

I have some free time for the next month, and should be able to knock out a
basic wiki system in this time (I found what looks like a nice book about
wikis that I could read and use as a guide for implementing it).

Since getting feedback on my presentation for Guix Days, where I think a
lot of good criticism was raised, I've been thinking about ways to organize
contributions to the docs. An idea I've had is to create a wiki that has a
basic system of tags that can link with Mumi so that while folks are
looking things up they can also get a sense if there are "TODOs" concerning
a subject they reading up on, even beyond contributing to the docs. Many
folks have expressed that they want to start chipping in, but aren't quite
sure where to start. Perhaps something like this could help ease that
process, and make updating information more dynamic and less critical than
in the main docs.

Any thoughts?

ez,
b

On Tue, Jun 28, 2022, 20:26 Luis Felipe <luis.felipe.la@protonmail.com>
wrote:

> Hi Blake,
>
> On Monday, June 27th, 2022 at 06:57, Blake Shaw <blake@sweatshoppe.org>
> wrote:
>
> > Finally I caved and decided to look at the Bootstrappable source code,
> and
> > voila! (haunt html) provides sxml->html... the piece of the puzzle I was
> > missing. Massive, near comical, relief.
>
> Just to mention that there is also htmlprag, from guile-lib (
> https://www.nongnu.org/guile-lib/doc/ref/htmlprag/).

[-- Attachment #2: Type: text/html, Size: 2905 bytes --]

  reply	other threads:[~2022-06-28 18:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-27  6:57 [feature request] merge sxml->html from (haunt html) into guile? Blake Shaw
2022-06-28 13:26 ` Luis Felipe
2022-06-28 18:34   ` Blake Shaw [this message]
2022-06-28 20:13     ` Wiki && " Maxime Devos
2022-06-28 21:05       ` Maxime Devos
2022-06-29  3:26       ` bokr
2022-06-29  6:19       ` Dr. Arne Babenhauserheide
  -- strict thread matches above, loose matches on Subject: below --
2022-06-28 19:57 dsmich

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://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAKjmbcDH8S90FW+xwo7XppU9G=qhTcYJUDPzU2Z9XHAHqLX87g@mail.gmail.com' \
    --to=blake@sweatshoppe.org \
    --cc=guile-user@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=luis.felipe.la@protonmail.com \
    /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).