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: Browser based editor for markdown
Date: Mon, 27 May 2019 17:42:35 +0100	[thread overview]
Message-ID: <886828E4-4386-43A6-A142-D5718A7879A2@ipfire.org> (raw)
In-Reply-To: <CAK9whhyxvXiOaB=S5Y2dyMc+7_GFhZheXtrMna+S4aOEhO-gQQ@mail.gmail.com>

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

Hey Carlo,

> On 27 May 2019, at 17:39, Carlo Fusco <fusco.carlo(a)gmail.com> wrote:
> 
> I don't understand the issue at all, therefore my apologies if I waste
> your time with this link.

No worries about wasting my time :)

> Would this be useful?
> 
> https://github.com/hackmdio/codimd
> 
> I saw a discussion on hacker news about editors and someone mentioned
> HackMD (CodiMD is the free software incarnation of it) as a good
> collaborative, markdown editor. I cannot find out if it can be
> embedded in a page, the only thing I could find is the possibility to
> use an iframe to embed a note:
> 
> https://github.com/hackmdio/codimd/blob/4e596d724dcb1a5a19ab1e75df250767334ebfc9/public/docs/features.md#embed-a-note
> 
> I do not understand if this is something you can work with, so I
> mention it just in case.

As far as I understand this, it is a word processor where you write markdown and export it as a PDF or something else.

It has the editor element, but also syncs this between browsers and what not. That is all something we do not need.

-Michael

> 
> On Mon, May 27, 2019 at 4:53 PM Michael Tremer
> <michael.tremer(a)ipfire.org> wrote:
>> 
>> Hi Jon,
>> 
>> This is definitely a tool that I would like to have integrated into the wiki.
>> 
>> However, that is not possible:
>> 
>>  https://github.com/benweet/stackedit/issues/150
>> 
>> I could not find anything else. The PageDown tool being mentioned in the thread seems to be quite old and no longer maintained. Of course I would like to avoid jumping from one piece of software that is a bit old to another one.
>> 
>> But I like this tool :)
>> 
>> -Michael
>> 
>>> On 26 May 2019, at 18:42, Jon Murphy <jcmurphy26(a)gmail.com> wrote:
>>> 
>>> Maybe this will help.  It is updated!
>>> 
>>> Jon
>>> 
>>> https://stackedit.io/app#
>>> 
>>> https://stackedit.io
>>> 
>>> https://github.com/benweet/stackedit
>>> 
>>> _______________________________________________
>>> Documentation mailing list
>>> Documentation(a)lists.ipfire.org
>>> https://lists.ipfire.org/mailman/listinfo/documentation
>> 
>> _______________________________________________
>> Documentation mailing list
>> Documentation(a)lists.ipfire.org
>> https://lists.ipfire.org/mailman/listinfo/documentation
> 
> 
> 
> -- 
> Carlo Fusco


      reply	other threads:[~2019-05-27 16:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-26 17:42 Jon Murphy
2019-05-27 14:53 ` Michael Tremer
2019-05-27 16:39   ` Carlo Fusco
2019-05-27 16:42     ` Michael Tremer [this message]

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=886828E4-4386-43A6-A142-D5718A7879A2@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