From: Kaushal Modi <kaushal.modi@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Luis Roca <roca@pobox.com>, Diego Zamboni <diego@zzamboni.org>,
emacs-orgmode@gnu.org
Subject: Re: Moving from Jekyll to Orgmode
Date: Fri, 04 May 2018 13:53:00 +0000 [thread overview]
Message-ID: <CAFyQvY12RS+yvfcdk0gM34jx0SwJaBNwMPEeHNZbrsP25t4YFQ@mail.gmail.com> (raw)
In-Reply-To: <CAFyQvY3yWSyecnLzsk0_fEXt8pi6qW+298UJ1mjkrheVQcfNuw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1298 bytes --]
Hello Thomas,
I forgot to expand a bit on this part..
On Fri, May 4, 2018 at 9:43 AM Kaushal Modi <kaushal.modi@gmail.com> wrote:
>
>
>> I use org-mode for writing these kinds of thing now, and
>> I'm hoping to work out a way to make my org mode source work with
>> Hugo.
>>
>
> At minimum you just need the #+hugo_base_dir keyword and EXPORT_FILE_NAME
> property (if using per-subtree flow). So it should not be too difficult. To
> get an idea, I made these[1] changes to make the pre-existing use-package
> Org manual ready for ox-hugo export.
>
I port some of my pre-existing notes in Org format to my blog as I get
time. Here's a recent one..
Org source:
https://gitlab.com/kaushalmodi/kaushalmodi.gitlab.io/raw/master/content-org/notes/awk/awk.org
The only lines added to it for exporting (using the per-file flow) using
ox-hugo were:
#+hugo_base_dir: ../../../
#+hugo_section: notes
#+hugo_bundle: awk
#+export_file_name: index
#+hugo_categories: unix
#+hugo_tags: awk
And I added this Org Special block supported by ox-hugo:
#+begin_description
Collection of ~awk~ examples.
#+end_description
With that in place, I exported the Markdown file, committed it to my repo,
Netlify ran hugo to regenerate my site, and deployed it to
https://scripter.co/notes/awk/.
--
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 2235 bytes --]
next prev parent reply other threads:[~2018-05-04 13:53 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
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 [this message]
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=CAFyQvY12RS+yvfcdk0gM34jx0SwJaBNwMPEeHNZbrsP25t4YFQ@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--cc=diego@zzamboni.org \
--cc=emacs-orgmode@gnu.org \
--cc=roca@pobox.com \
--cc=tsd@tsdye.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).