Hi,
It looks like this was only broken for the index page.
I pushed out some changes. Please try again.
-Michael
On 30 May 2019, at 18:04, Jon Murphy jcmurphy26@gmail.com wrote:
Michael - The preview does not work for me. I see the word "Preview" and then to the far right I see a spinning circle. Below that I see "Loading...".
Jon
<Screen Shot 2019-05-30 at 11.45.40 AM.png>
From: Michael Tremer Sent: Thursday, May 30, 2019, 9:50 AM To: Matthias Fischer Cc: Jon Murphy; documentation@lists.ipfire.org Subject: Re: New Wiki Software - Please help testing :)
Okay, I just pushed some changes.
There is now a preview function which automatically updates. I quite like it. Tell me what you think.
Preview works! Yay!
But I still get this error: Failed to load resource: the server responded with a status of 404 () https://wiki.dev.ipfire.org/static/js/popper.min.js https://wiki.dev.ipfire.org/static/js/popper.min.js.map
From: Michael Tremer Sent: Thursday, May 30, 2019, 12:22 PM To: Jon Murphy Cc: documentation@lists.ipfire.org, Matthias Fischer Subject: Re: New Wiki Software - Please help testing :)
Hi,
It looks like this was only broken for the index page.
I pushed out some changes. Please try again.
-Michael
On 30 May 2019, at 18:04, Jon Murphy jcmurphy26@gmail.com wrote:
Michael - The preview does not work for me. I see the word "Preview" and then to the far right I see a spinning circle. Below that I see "Loading...".
Jon
<Screen Shot 2019-05-30 at 11.45.40 AM.png>
From: Michael Tremer Sent: Thursday, May 30, 2019, 9:50 AM To: Matthias Fischer Cc: Jon Murphy; documentation@lists.ipfire.org Subject: Re: New Wiki Software - Please help testing :)
Okay, I just pushed some changes.
There is now a preview function which automatically updates. I quite like it. Tell me what you think.
I just updated popper.js. Error is gone.
So how are the changes to the wiki?
On 30 May 2019, at 18:24, Jon Murphy jcmurphy26@gmail.com wrote:
Preview works! Yay!
But I still get this error: Failed to load resource: the server responded with a status of 404 () https://wiki.dev.ipfire.org/static/js/popper.min.js.map
From: Michael Tremer Sent: Thursday, May 30, 2019, 12:22 PM To: Jon Murphy Cc: documentation@lists.ipfire.org, Matthias Fischer Subject: Re: New Wiki Software - Please help testing :)
Hi,
It looks like this was only broken for the index page.
I pushed out some changes. Please try again.
-Michael
On 30 May 2019, at 18:04, Jon Murphy jcmurphy26@gmail.com wrote:
Michael - The preview does not work for me. I see the word "Preview" and then to the far right I see a spinning circle. Below that I see "Loading...".
Jon
<Screen Shot 2019-05-30 at 11.45.40 AM.png>
From: Michael Tremer Sent: Thursday, May 30, 2019, 9:50 AM To: Matthias Fischer Cc: Jon Murphy; documentation@lists.ipfire.org Subject: Re: New Wiki Software - Please help testing :)
Okay, I just pushed some changes.
There is now a preview function which automatically updates. I quite like it. Tell me what you think.
Much, much easier with the preview! Thank you for adding this!
I saw the note about <img>. When using a pure markdown (versus an html <img>) there is no ability to size images. Which means an image must be sized before loading into the wiki. How are new images loaded into the wiki? And what directory do they load into?
Jon
From: Michael Tremer Sent: Thursday, May 30, 2019, 12:31 PM To: Jon Murphy Cc: documentation@lists.ipfire.org, Matthias Fischer Subject: Re: New Wiki Software - Please help testing :)
I just updated popper.js. Error is gone.
So how are the changes to the wiki?
Hi,
On 30 May 2019, at 18:40, Jon Murphy jcmurphy26@gmail.com wrote:
Much, much easier with the preview! Thank you for adding this!
Great. You are welcome!
I saw the note about <img>. When using a pure markdown (versus an html <img>) there is no ability to size images. Which means an image must be sized before loading into the wiki. How are new images loaded into the wiki? And what directory do they load into?
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.
Every namespace has an extra page to upload images. Just append /_files to the URL:
https://wiki.dev.ipfire.org/installation/_files
If you click on an image, it has an example on how it is being embedded into the markup.
This page uses those images for example: https://wiki.dev.ipfire.org/installation/step3
Check out the caption. I like that one a lot :)
-Michael
Jon
From: Michael Tremer Sent: Thursday, May 30, 2019, 12:31 PM To: Jon Murphy Cc: documentation@lists.ipfire.org, Matthias Fischer Subject: Re: New Wiki Software - Please help testing :)
I just updated popper.js. Error is gone.
So how are the changes to the wiki?
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.
This page uses those images for example: https://wiki.dev.ipfire.org/installation/step3 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!)
Hi,
On 30 May 2019, at 20:02, Jon Murphy jcmurphy26@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 :)
Works well!
I'm glad you added the example. Is a double brace (curly brackets?) new to Markdown? It is something I hadn't seen before.
None of the images have any. But in the example there was one:
{{image.png|This is a caption}}
Try it :)
Hi,
No this is not markdown.
Markdown would be ![Caption](/image.png).
Would you prefer that syntax? Is that better?
-Michael
On 30 May 2019, at 20:23, Jon Murphy jcmurphy26@gmail.com wrote:
Works well!
I'm glad you added the example. Is a double brace (curly brackets?) new to Markdown? It is something I hadn't seen before.
None of the images have any. But in the example there was one:
{{image.png|This is a caption}}
Try it :)
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. ![Caption](/image.png) would be easier to remember for people that had used markdown.
No this is not markdown.
Markdown would be ![Caption](/image.png).
Would you prefer that syntax? Is that better?
-Michael
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@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. ![Caption](/image.png) would be easier to remember for people that had used markdown.
No this is not markdown.
Markdown would be ![Caption](/image.png).
Would you prefer that syntax? Is that better?
-Michael
Doesn't a link without a title become this:
<link>
https://daringfireball.net/projects/markdown/syntax#autolink https://daringfireball.net/projects/markdown/syntax#autolink
From: Michael Tremer Sent: Sunday, June 2, 2019, 5:13 PM To: Jon Murphy Cc: documentation@lists.ipfire.org, Matthias Fischer Subject: Re: New Wiki Software - Please help testing :)
But what do we do in the first case, when we do not want to write the title?
Does this look right? [](link)
documentation@lists.ipfire.org