From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: documentation@lists.ipfire.org Subject: Re: New Wiki Software - Please help testing :) Date: Mon, 27 May 2019 17:27:54 +0100 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8638496708880005645==" List-Id: --===============8638496708880005645== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable 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 abo= ut those: * You used absolute links: This is something that should not be done when lin= king other pages on the wiki. I have spent a lot of time to make the code fas= t enough when it fetches the headline of the page so that we will show the co= rrect headline. The absolute links don=E2=80=99t work like that. So wiki links are possible just as they were before with [[page]] and [[page#= Other Title]]. * You used the tag to embed an image. The image pages have a short snip= pet to embed the image: https://wiki.dev.ipfire.org/ipfire_tux_512x512.png?action=3Ddetail 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=E2=80= =99t work. We don=E2=80=99t know how large the screen is someone is using. * Matthias saved the same page a couple of times. That definitely shows that = we need a preview function :) I do not want to point any fingers here at all. But I learned things from thi= s. If it felt natural for you to do these things, but it was meant in another= way then this is a bug in the software. But I have no idea how to find a good solution for this. Admittedly nothing i= s documented yet, but future editors might not read the documentation. People= edit first and I do want anyone to edit this wiki. We care about the informa= tion first, but we need to make sure that people do not mess up the markup. I think that Dokuwiki is quite bad in that sense that it allows to be messy w= ith the markup. This is also why conversion into another language is so diffi= cult. There is multiple ways to do something and they can be mixed. Horror. So what springs to mind here is: We could refuse saving the page when somethi= ng is not right. But I think that might feel very frustrating. An tag s= hould never show up. If we find that, then we can just throw an error. What do you guys think could work? -Michael P.S. I pushed out a couple of fixes, but I do not have a preview function yet= . Not sure whether I can make that update live or if we will have a button. O= r maybe a two-step save process. I need to explore that a little. Please send= me your thoughts in case you have any ideas. But make them easy to implement= :) > On 24 May 2019, at 23:03, Jon Murphy wrote: >=20 > Michael - It seems like there are some differences between Markdown and the= new wiki app. One is the double brackets, e.g., [[relativeLink]] >=20 > With the old wiki I could search thru the Dokuwiki website for hints. What = is the name of the new app? That will give us a better idea of how to use it. >=20 > Jon > _______________________________________________ > Documentation mailing list > Documentation(a)lists.ipfire.org > https://lists.ipfire.org/mailman/listinfo/documentation --===============8638496708880005645==--