emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Thomas S. Dye" <tsd@tsdye.com>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: Luis Roca <roca@pobox.com>, Diego Zamboni <diego@zzamboni.org>,
	emacs-orgmode@gnu.org
Subject: Re: Moving from Jekyll to Orgmode
Date: Thu, 03 May 2018 20:49:53 -1000	[thread overview]
Message-ID: <87zi1fykxa.fsf@tsdye.com> (raw)
In-Reply-To: <CAFyQvY1OinHDWyH-vPMwmqMn7=rc-JXtsWscpGeT_HxhHym5fQ@mail.gmail.com>

Aloha Kaushal

Kaushal Modi writes:
>
>> I really recommend ox-hugo, Kaushal has done a fantastic job 
>> and he is
>> also really helpful and responsive with questions.
>>
>
> Thanks for this heavy recommendation. Working on this project 
> and
> supporting/making it more robust based on user feedback has been 
> great
> pleasure.

This looks like an interesting project.

I've browsed the various Hugo themes and the example web sites. I 
think I've seen websites similar to and themes suitable for a 
variety of sites I'd like to consolidate: archaeology course 
syllabus and class calendar; documentation for a software project; 
a publication list with download links; and a book/article review 
blog.  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.

I'm especially keen on previewing the web pages as I work on them, 
which was super easy to set up (thanks!), and generating 
"responsive" content to satisfy my smartphone connected students.

I see that ox-hugo and many Hugo templates have a blog as their 
focus.  Is it reasonable to go down the ox-hugo path for my 
planned sites?  Or, is the blog focus likely to restrict what I'd 
like to do?

All the best,
Tom

--
Thomas S. Dye
http://www.tsdye.com

  parent reply	other threads:[~2018-05-04  6: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
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 [this message]
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=87zi1fykxa.fsf@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=diego@zzamboni.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=kaushal.modi@gmail.com \
    --cc=roca@pobox.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).