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: Thu, 18 Jul 2019 11:16:52 +0100 Message-ID: <5BDECB3F-9E3B-4001-B112-2EA847A0D670@ipfire.org> In-Reply-To: <2BED6F14-2001-4C45-8676-98462927955C@gmail.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1574429234494551958==" List-Id: --===============1574429234494551958== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, > On 17 Jul 2019, at 23:57, Jon Murphy wrote: >=20 > Does this mean using only the Basic Syntax (John Gruber=E2=80=99s original = design)? In my opinion, the basic syntax is not complete. I=E2=80=99d strongl= y suggest using the extended syntax (https://www.markdownguide.org/extended-s= yntax). No, this is the extended syntax that we are using here. >=20 > Will HTML be restricted? From Basic Syntax Markdown Guide (https://www.mar= kdownguide.org/basic-syntax/): =20 No, not for now. But there is absolutely no point in using it. Everything should be markdown. I will implement filtering HTML tags soon when= there is time for it. >=20 > Note: Using Markdown doesn't mean that you can't also use HTML. You can = add HTML tags to any Markdown file. This is helpful if you prefer certain HTM= L tags to Markdown syntax. For example, some people find that it's easier to = use HTML tags for images. Please don=E2=80=99t do that. What is the point of markdown in the first plac= e then? This will break the layout, make it impossible to render the documentation in= to PDF and many things more. -Michael >=20 >=20 >>=20 >> I changed from the markdown2 python module back to the default one which s= eems to be used more often. I think we should stick very closely to the origi= nal markdown syntax. I find that one quite loose already and it allows 10 dif= ferent ways to do the same thing, but this is what people are used to. >>=20 >=20 --===============1574429234494551958==--