From: John Hendy <jw.hendy@gmail.com>
To: Puneeth Chaganti <punchagan@gmail.com>
Cc: Jeffrey Brent McBeth <mcbeth@broggs.org>,
emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: org to static site?
Date: Wed, 31 May 2017 11:17:56 -0500 [thread overview]
Message-ID: <CA+M2ft9KgD_0dddu57FQNqMdyRLSm9m2jwRnwHwNC0DHNvRmxA@mail.gmail.com> (raw)
In-Reply-To: <CALnw1fRuXBABgc6=k-owUPop4wvixSF=VBmZ8SfgRGETCFjq4g@mail.gmail.com>
On Wed, May 31, 2017 at 11:08 AM, Puneeth Chaganti <punchagan@gmail.com> wrote:
> I really wrestled with getting it to behave initially. I hope the
> intro to the docs is a joke, as either I'm an idiot or the author
> definitely failed :)
> - https://getnikola.com/handbook.html
>
> "DON'T READ THIS MANUAL. IF YOU NEED TO READ IT I FAILED, JUST USE THE
> THING."
>
>
> To be fair to the author, org support is not built into Nikola, and is
> coming through a plugin (by yours truly). The remote calls to Emacs for
> compiling, and other ugly stuff can make it harder than necessary to deal
> with.
Understood, and I just meant in general (not org integration). This
was a bit tongue in cheek; I don't think anyone would *expect* that
something like this could be used without a manual. It's complicated
and takes a bit to parse, just like any other software! I think it's
great thus far, but can't fathom how someone could "pick it up" and
start using it from scratch with no docs.
John
> - Puneeth
next prev parent reply other threads:[~2017-05-31 16:17 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 15:00 org to static site? Matt Price
2017-05-31 15:08 ` Russell Adams
2017-05-31 15:17 ` Jeffrey Brent McBeth
2017-05-31 15:29 ` Russell Adams
2017-05-31 15:34 ` John Hendy
2017-05-31 16:20 ` Russell Adams
2017-05-31 16:37 ` John Kitchin
2017-05-31 15:32 ` John Hendy
2017-05-31 16:08 ` Puneeth Chaganti
2017-05-31 16:17 ` John Hendy [this message]
2017-05-31 17:05 ` Chunyang Xu
2017-05-31 19:51 ` John Ankarström
2017-05-31 18:23 ` lists
2017-06-01 7:46 ` Julian M. Burgos
2017-06-01 10:09 ` Rasmus
2017-06-04 18:26 ` Scott Randby
2017-06-05 5:59 ` John Ankarström
2017-06-05 16:54 ` Scott Randby
2017-06-05 21:16 ` Nick Dokos
2017-06-06 2:41 ` Scott Randby
2017-06-10 9:21 ` Nicolas Goaziou
2017-06-10 18:13 ` Scott Randby
2017-06-06 9:12 ` Fabrice Popineau
2017-06-08 8:14 ` Ken Mankoff
2017-11-30 5:13 ` George myglc2 Clemmer
2017-12-01 17:17 ` Tory S. Anderson
2017-12-01 21:13 ` George myglc2 Clemmer
2017-12-01 20:19 ` Adonay Felipe Nogueira
2017-12-02 2:53 ` myglc2
2017-12-05 12:30 ` Rasmus
2017-12-05 16:40 ` myglc2
2017-12-05 19:10 ` ox-publish export subtree scopes? (Was: org to static site?) Kaushal Modi
2017-12-10 7:15 ` ox-publish export subtree scopes? Narendra Joshi
2017-12-19 11:53 ` Rasmus
2018-01-15 21:27 ` Adonay Felipe Nogueira
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=CA+M2ft9KgD_0dddu57FQNqMdyRLSm9m2jwRnwHwNC0DHNvRmxA@mail.gmail.com \
--to=jw.hendy@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mcbeth@broggs.org \
--cc=punchagan@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).