public inbox for documentation@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: New Wiki Software - Please help testing :)
Date: Thu, 18 Jul 2019 11:16:52 +0100	[thread overview]
Message-ID: <5BDECB3F-9E3B-4001-B112-2EA847A0D670@ipfire.org> (raw)
In-Reply-To: <2BED6F14-2001-4C45-8676-98462927955C@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1452 bytes --]

Hi,

> On 17 Jul 2019, at 23:57, Jon Murphy <jcmurphy26(a)gmail.com> wrote:
> 
> Does this mean using only the Basic Syntax (John Gruber’s original design)? In my opinion, the basic syntax is not complete. I’d strongly suggest using the extended syntax (https://www.markdownguide.org/extended-syntax).

No, this is the extended syntax that we are using here.

> 
> Will HTML be restricted?  From Basic Syntax Markdown Guide (https://www.markdownguide.org/basic-syntax/):  

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.

> 
>    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 HTML tags to Markdown syntax. For example, some people find that it's easier to use HTML tags for images.

Please don’t do that. What is the point of markdown in the first place then?

This will break the layout, make it impossible to render the documentation into PDF and many things more.

-Michael

> 
> 
>> 
>> I changed from the markdown2 python module back to the default one which seems to be used more often. I think we should stick very closely to the original markdown syntax. I find that one quite loose already and it allows 10 different ways to do the same thing, but this is what people are used to.
>> 
> 


  reply	other threads:[~2019-07-18 10:16 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
     [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
     [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=5BDECB3F-9E3B-4001-B112-2EA847A0D670@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