From: Michael Tremer <michael.tremer@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: New Wiki Software - Please help testing :)
Date: Sun, 02 Jun 2019 23:13:37 +0100 [thread overview]
Message-ID: <8B7D0E01-0BDB-404E-8D4E-195FF770E1A5@ipfire.org> (raw)
In-Reply-To: <FB49A1A9-366D-4AB6-81C6-F7CD879552D2@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1383 bytes --]
Hi,
So here is a question:
I thought it would be a good idea to extend the syntax of the wiki. I am not convinced that this is probably a bad idea.
Jon is right. People just know markdown. We should stick to it as closely as possible.
I can change the images, that is very quickly done.
But my question would now be about the links.
Right now we have this format: [[link]]
This even fetches the headline from the page called “link” so that everywhere in the wiki, the correct title is being used.
There is also the option of this: [[link|Another Text]]
That way, the text can be changed.
Markdown links look like this: [Text](link)
I am fine with the syntax. It is well known, etc.
But what do we do in the first case, when we do not want to write the title?
Does this look right? [](link)
-Michael
> On 30 May 2019, at 20:30, Jon Murphy <jcmurphy26(a)gmail.com> wrote:
>
> That is what I remember!
>
> Also from what I remember (and my memory is not good!) the [Caption] is more like an ALT text. I think it is called a tool tip and it pops up after a few moments.  would be easier to remember for people that had used markdown.
>
>
>> No this is not markdown.
>>
>> Markdown would be .
>>
>> Would you prefer that syntax? Is that better?
>>
>> -Michael
>>
>
next prev parent reply other threads:[~2019-06-02 22:13 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
[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
[not found] <3917C587-0660-4EA5-A997-081C3A69D045@gmail.com>
2019-05-30 18:17 ` Michael Tremer
[not found] <0E1A43E9-96F5-487C-8974-ED25DC70D05B@gmail.com>
2019-05-30 17:31 ` 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] <AF378EE0-6263-41AA-A6A0-5442D9C5FCC3@gmail.com>
2019-05-30 14:50 ` Michael Tremer
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
-- strict thread matches above, loose matches on Subject: below --
2019-05-24 16:48 Jon Murphy
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
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
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=8B7D0E01-0BDB-404E-8D4E-195FF770E1A5@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