From: Michael Tremer <michael.tremer@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: New Wiki Software - Please help testing :)
Date: Thu, 30 May 2019 15:50:58 +0100 [thread overview]
Message-ID: <998DA55B-ABF0-4CFA-BD1F-15E8D18D96BA@ipfire.org> (raw)
In-Reply-To: <AF378EE0-6263-41AA-A6A0-5442D9C5FCC3@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1802 bytes --]
Hi,
> On 28 May 2019, at 03:59, Jon Murphy <jcmurphy26(a)gmail.com> wrote:
>
> Just so I understand - Is this an example of the absolute link you are referring to?
> https://wiki.dev.ipfire.org/installation
>
> Or is a link like this?
> /installation
>
> Sorry, I just want to make sure I do things correct.
Yes, that would have been an absolute URL.
The advantage of using [[/installation]] is that the software fetches the title of the link and we might make links a different colour if the page does not exist or something.
-Michael
>
> Jon
> From: Michael Tremer
> Sent: Monday, May 27, 2019, 11:27 AM
> To: Jon Murphy
> Cc: documentation(a)lists.ipfire.org
> Subject: Re: New Wiki Software - Please help testing :)
>
>
> Hello,
>
> Yes, there are differences in plain markdown.
>
> I have seen that you did a couple of changes and I have a couple of notes about those:
>
> * You used absolute links: This is something that should not be done when linking other pages on the wiki. I have spent a lot of time to make the code fast enough when it fetches the headline of the page so that we will show the correct headline. The absolute links don’t work like that.
>
> So wiki links are possible just as they were before with [[page]] and [[page#Other Title]].
>
> * You used the <img> tag to embed an image. The image pages have a short snippet to embed the image:
>
> https://wiki.dev.ipfire.org/ipfire_tux_512x512.png?action=detail
>
> All images will always be full widths by default (and there is no reason not do to that) because all pages have to be responsive and we need to be able to read them on mobile. So using custom heights and widths naturally won’t work. We don’t know how large the screen is someone is using.
>
next parent reply other threads:[~2019-05-30 14:50 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AF378EE0-6263-41AA-A6A0-5442D9C5FCC3@gmail.com>
2019-05-30 14:50 ` 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] <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] <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
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=998DA55B-ABF0-4CFA-BD1F-15E8D18D96BA@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