unofficial mirror of emacs-tangents@gnu.org
 help / color / mirror / Atom feed
From: Amin Bandali <bandali@gnu.org>
To: Van L <van@scratch.space>
Cc: emacs-tangents@gnu.org
Subject: Re: emacs friendly platform like dokuwiki&zulip
Date: Sat, 29 Jun 2019 13:10:47 -0400	[thread overview]
Message-ID: <87pnmw71wo.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <m27e9xr6ri.fsf@scratch.space>

Hello,

Van L <van@scratch.space> writes:

> Hello,
>
> What are the emacs friendly platforms out there
> for blogging, wiki, chat threading?
>
> _Use case:_ to share what you want from Org Mode and
> Hyperbole in your files.
>
> _For example:_ I've figured out how to get all the
> fonts to display for 'M-x view-hello-file' and want
> that to be listed freely on a domain name I own

Seconding Alan’s suggestion of org-publish.  Besides that, org-page [0]
and org-static-blog [1] come to mind as well for static sites/blogs.

[0]: https://github.com/sillykelvin/org-page
[1]: https://github.com/bastibe/org-static-blog

Since you mentioned dokuwiki, if you don’t mind a non-static
alternative, I’ll raise you Oddmuse [2], another wiki engine that’s been
around for a good while.  It supports a number of different markups, and
there’s a version supporting Org [3], but sadly it doesn’t seem to be
actively maintained.  It may still be worth looking into though.

Regarding its emacs-friendliness, there’s an Oddmuse mode [4] that I’ve
been meaning to look into but haven’t gotten around to yet.  If you end
up trying it out, I’d be interested in hearing your experience with it.

[2]: https://oddmuse.org
[3]: https://oddmuse.org/wiki/Org_Markup_Extension
[4]: https://www.emacswiki.org/emacs/OddmuseMode

-amin



  parent reply	other threads:[~2019-06-29 17:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-07 11:09 emacs friendly platform like dokuwiki&zulip Van L
2019-06-07 18:40 ` Alan Third
2019-06-12  5:04   ` Van L
2019-06-29 17:10 ` Amin Bandali [this message]
2019-07-28  7:47   ` VanL

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pnmw71wo.fsf@fencepost.gnu.org \
    --to=bandali@gnu.org \
    --cc=emacs-tangents@gnu.org \
    --cc=van@scratch.space \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).