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 20:04:12 +0100 [thread overview]
Message-ID: <11644E7D-E9F5-4526-92F0-7092C67A73FC@ipfire.org> (raw)
In-Reply-To: <4BB6A887-545C-4194-B497-16E08FE82231@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1294 bytes --]
Hi,
> On 30 May 2019, at 20:02, Jon Murphy <jcmurphy26(a)gmail.com> wrote:
>
>
>>
>> Yeah, so images are difficult. Please do not size them before uploading them.
>>
>> When writing the wiki, I found that there is no point in having an image that is not full width. What would that be? Screenshots are full size. Logos and so on can also fill the whole screen. Consider that we do not know the screen size of the user. Having an image sized to half the width of the white column would maybe work on your desktop, but not on someones much smaller phone screen.
>>
>
> The only reasons I know of is visual appeal and faster page loads (for a smaller sized image). And agreed, screenshots are full size.
I forgot to mention that the wiki of course scales them down and I spent quite a lot of time on compressing the images as much as possible. So don’t worry about that.
>>
>> This page uses those images for example: https://wiki.dev.ipfire.org/installation/step3
>>
>> Check out the caption. I like that one a lot :)
>>
>
> I don't find any captions. I must be looking in the wrong place or at the wrong image! (My wife says I am blind!)
None of the images have any. But in the example there was one:
{{image.png|This is a caption}}
Try it :)
next parent reply other threads:[~2019-05-30 19:04 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 [this message]
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
[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=11644E7D-E9F5-4526-92F0-7092C67A73FC@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