From: ST <smntov@gmail.com>
To: Scott Randby <srandby@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Moving from Jekyll to Orgmode
Date: Sun, 29 Apr 2018 11:50:12 +0300 [thread overview]
Message-ID: <1524991812.21032.180.camel@gmail.com> (raw)
In-Reply-To: <50f36953-4528-91f1-d4c9-05228a967f11@gmail.com>
Hi Scott,
thank you, and all other responders, for the shared information. The
reason I want to leave Jekyll is because I don't want to depend on a
tool that relies on language (Ruby)/environment that I don't know/use
(in this respect Hugo is the same for me). I prefer something more
simplistic, even though if I'll have to invest some time for it to work
initially. Those 3 features I've mentioned are almost all I need, more
or less.
Could you, please, share your website publishing workflow (considering
the 3 issues I've mentioned)?
Thank you!
On Sat, 2018-04-28 at 18:13 -0400, Scott Randby wrote:
> On 04/28/2018 05:40 PM, Diego Zamboni wrote:
> >
> > Org-mode is not really a website-publishing tool like Jekyll, although it can be part of the chain. Org-mode at its core is a markup language, although with considerable tooling support from org-mode and related tools in Emacs.
> >
>
> I think Org is a good website publishing tool in many ways. I've been using it for making and publishing my website since 2010. Sure, it has some limitations, but I think it can be made to work nicely for a lot of types of sites. But I do agree that the Org/Hugo combination is really good.
>
> Scott Randby
>
next prev parent reply other threads:[~2018-04-29 8:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-28 21:05 Moving from Jekyll to Orgmode ST
2018-04-28 21:40 ` Diego Zamboni
2018-04-28 21:42 ` Diego Zamboni
2018-04-28 22:13 ` Scott Randby
2018-04-29 8:50 ` ST [this message]
2018-04-29 9:07 ` Bastien
2018-04-29 9:22 ` ST
2018-04-29 12:58 ` Ista Zahn
2018-04-29 14:45 ` Scott Randby
2018-04-29 7:45 ` Saša Janiška
2018-04-29 12:55 ` Luis Roca
2018-04-30 20:28 ` Diego Zamboni
2018-04-30 22:43 ` Kaushal Modi
2018-05-01 18:41 ` Diego Zamboni
2018-05-04 6:49 ` Thomas S. Dye
2018-05-04 13:43 ` Kaushal Modi
2018-05-04 13:53 ` Kaushal Modi
2018-05-04 15:07 ` Thomas S. Dye
2018-04-29 16:45 ` Grant Rettke
2018-04-30 10:58 ` ST
2018-05-05 17:51 ` Rasmus
2018-05-07 8:39 ` ST
2018-05-07 22:21 ` Rasmus
2018-05-09 7:35 ` ST
2018-05-09 8:03 ` Thomas S. Dye
2018-05-09 12:37 ` ST
2018-05-09 11:38 ` Diego Zamboni
2018-05-09 12:21 ` Kaushal Modi
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1524991812.21032.180.camel@gmail.com \
--to=smntov@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=srandby@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).