From: "Jonathan McHugh" <indieterminacy@libre.brussels>
To: "Matt" <matt@excalamus.com>, "Vagrant Cascadian" <vagrant@debian.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Guix wiki
Date: Tue, 11 Jan 2022 18:29:53 +0000 [thread overview]
Message-ID: <3370e9e9e0854967a56f379ded5b6069@libre.brussels> (raw)
In-Reply-To: <17e493b8183.123074b03253860.2328518260869520673@excalamus.com>
Hi Matt,
Thanks for an interesting and thoughtful thread.
FYI, I am developing an interpreting application that will be mixing Emacs-Hyperboles tree orientated format with Gemini protocol's GemText format (as well as some classification approaches). Potentially it can (eventually) make a good fit for a wiki.
I will be presenting some aspects around it for Fosdem
=> https://fosdem.org/2022/schedule/event/minimalsyntaxes/
Kind regards,
====================
Jonathan McHugh
indieterminacy@libre.brussels
January 11, 2022 3:24 PM, "Matt" <matt@excalamus.com> wrote:
>> There are definitely wikis which use fairly simple markup
>
>> (e.g. markdown) and can usefully be read and updated online via a web
>> interface and git offline or online. The one I'm most familiar with is
>> ikiwiki (available in guix), though don't have a lot of experience
>> updating it via the web interface.
>
> It looks like the web interface is simple yet sufficient, basically a text box and then the buttons
> you'd expect: submit, preview, add/remove attachment. It uses the usual markdown syntax and can
> support others using plugins.
>
> https://ikiwiki.info/ikiwiki/formatting
>
> The default style is pretty bare bones, but I imagine it could be made to match the Guix theme.
>
> Great suggestion!
next prev parent reply other threads:[~2022-01-11 18:30 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 21:14 Guix wiki Matt
2022-01-09 21:32 ` Vagrant Cascadian
2022-01-11 13:02 ` Matt
2022-01-11 18:29 ` Jonathan McHugh [this message]
2022-04-13 14:46 ` Aurora
2022-01-09 23:55 ` Vincent Legoll
2022-01-11 13:31 ` Matt
2022-01-11 15:17 ` Ricardo Wurmus
2022-01-12 2:52 ` Matt
2022-01-11 15:30 ` Tobias Geerinckx-Rice
2022-01-11 17:15 ` zimoun
2022-01-11 17:27 ` Tobias Geerinckx-Rice
2022-01-11 18:21 ` André A. Gomes
2022-01-11 18:50 ` zimoun
2022-01-12 2:06 ` Tobias Geerinckx-Rice
2022-01-12 8:55 ` zimoun
2022-01-12 9:22 ` André A. Gomes
2022-01-12 3:51 ` Matt
2022-01-12 15:26 ` Luis Felipe
2022-01-11 16:48 ` Luis Felipe
2022-01-11 21:03 ` Attila Lendvai
2022-01-11 23:18 ` Ricardo Wurmus
2022-01-12 3:28 ` Matt
2022-01-18 14:34 ` Ludovic Courtès
2022-04-11 6:49 ` Attila Lendvai
2022-04-11 8:42 ` Maxime Devos
2022-04-13 15:01 ` Attila Lendvai
2022-04-11 8:47 ` Maxime Devos
2022-01-12 11:19 ` Attila Lendvai
2022-01-12 11:52 ` Ricardo Wurmus
2022-01-12 12:00 ` André A. Gomes
2022-01-10 8:29 ` Josua Stingelin
2022-01-12 1:57 ` Matt
2022-01-12 9:19 ` Ricardo Wurmus
2024-01-10 9:55 ` Attila Lendvai
2024-01-17 19:17 ` Maxim Cournoyer
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=3370e9e9e0854967a56f379ded5b6069@libre.brussels \
--to=indieterminacy@libre.brussels \
--cc=guix-devel@gnu.org \
--cc=matt@excalamus.com \
--cc=vagrant@debian.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).