From: Michael Tremer <michael.tremer@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: New Wiki Software - Please help testing :)
Date: Sun, 26 May 2019 11:54:32 +0100 [thread overview]
Message-ID: <3357E999-1720-435C-87C4-827EB40B495B@ipfire.org> (raw)
In-Reply-To: <b81afb01-4c5f-d650-4f80-230b37b6ba42@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1392 bytes --]
Hi,
> On 26 May 2019, at 09:28, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>
> Hi,
>
> Login seems to be ok, but I'm missing some things that would make
> editing much easier:
>
> - no ‘preview'
Would you guys like that?
> - no 'cancel' button ;-)
I thought you have a Back button :)
> - no toolbar with editing tools
I looked for a nice JS tool, but they are all unmaintained for ages. So that has to be written from scratch.
> - no 'playground' for testing
Just create the page :)
>
> Syntax should be no problem - I took a look at
> https://en.wikipedia.org/wiki/Markdown (is this the right language?).
Yes, although we have some extensions. Wiki links work like they used to before.
> I also found
> https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet
>
> There are a few examples here and there and this helps, but it would be
> great if we could get some kind of WUI for this in the future - an
> 'editor', as you wrote.
I will create a syntax reference as soon as we know that I do not have to re-import the whole thing.
Keep that in mind when you do any changes :)
-Michael
>
> JM2C for now - Best,
> Matthias
> _______________________________________________
> Documentation mailing list
> Documentation(a)lists.ipfire.org
> https://lists.ipfire.org/mailman/listinfo/documentation
next prev parent reply other threads:[~2019-05-26 10:54 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 13:35 Michael Tremer
2019-05-24 10:58 ` Carlo Fusco
2019-05-24 11:07 ` Carlo Fusco
2019-05-26 10:43 ` Michael Tremer
2019-05-26 8:28 ` Matthias Fischer
2019-05-26 10:54 ` Michael Tremer [this message]
2019-05-26 10:55 ` Michael Tremer
2019-06-01 12:09 ` ummeegge
2019-06-02 22:10 ` Michael Tremer
2019-06-06 3:30 ` Jon Murphy
2019-07-16 16:34 ` Michael Tremer
2019-05-24 16:48 Jon Murphy
2019-05-24 22:03 Jon Murphy
2019-05-27 16:27 ` Michael Tremer
2019-05-27 17:10 ` Matthias Fischer
2019-05-30 14:50 ` Michael Tremer
2019-05-28 3:05 ` Jon Murphy
2019-05-30 14:51 ` Michael Tremer
[not found] <AF378EE0-6263-41AA-A6A0-5442D9C5FCC3@gmail.com>
2019-05-30 14:50 ` Michael Tremer
[not found] <630732F1-CA01-43FD-8EB5-4601C6BF3162@gmail.com>
2019-05-30 17:07 ` Michael Tremer
2019-05-30 17:22 ` Michael Tremer
[not found] <0E1A43E9-96F5-487C-8974-ED25DC70D05B@gmail.com>
2019-05-30 17:31 ` Michael Tremer
[not found] <3917C587-0660-4EA5-A997-081C3A69D045@gmail.com>
2019-05-30 18:17 ` Michael Tremer
[not found] <4BB6A887-545C-4194-B497-16E08FE82231@gmail.com>
2019-05-30 19:04 ` Michael Tremer
2019-05-30 19:23 ` Jon Murphy
2019-05-30 19:24 ` Michael Tremer
2019-05-30 19:30 ` Jon Murphy
2019-06-02 22:13 ` Michael Tremer
[not found] <2CAE7946-C451-4D11-B3C6-9C64CAFC1220@gmail.com>
2019-07-17 15:57 ` Michael Tremer
2019-07-17 22:57 ` Jon Murphy
2019-07-18 10:16 ` Michael Tremer
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3357E999-1720-435C-87C4-827EB40B495B@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=documentation@lists.ipfire.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox