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: Fri, 04 May 2018 05:07:02 -1000 [thread overview]
Message-ID: <87y3gzbgtl.fsf@tsdye.com> (raw)
In-Reply-To: <CAFyQvY3yWSyecnLzsk0_fEXt8pi6qW+298UJ1mjkrheVQcfNuw@mail.gmail.com>
Aloha Kaushal,
Kaushal Modi writes:
> Hello Thomas,
>
> On Fri, May 4, 2018 at 2:50 AM Thomas S. Dye <tsd@tsdye.com>
> wrote:
>
>> 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.
>
>
> That's correct, you can use Hugo to generate any of those kinds
> of sites. I
> use it for my blog, the ox-hugo doc site itself, the bare-bones
> ox-hugo
> test site, product doc site at work. I have also used it in the
> past for a
> "for-rent" site in the past (and it worked ;-)).
>
>
>> 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'm especially keen on previewing the web pages as I work on
>> them,
>> which was super easy to set up (thanks!),
>
>
> Great! So I gather that you were able to get a preliminary setup
> of
> ox-hugo + Hugo working?
Yes, your ox-hugo test site was up and running in a few minutes.
Every few seconds new blog entries would pop up on my browser as
Hugo processed the test file.
The hardest part for me was getting ox-hugo to work in spacemacs.
This isn't an ox-hugo thing. I've had problems with other org
mode components in spacemacs, mostly having to do with the order
things are loaded.
>
>
>> and generating "responsive" content to satisfy my smartphone
>> connected
>> students.
>>
>
> That part is not too difficult if you want to get the basic
> responsiveness.. just adding the viewport meta tag in HTML head
> does most
> of the job:
>
> <meta name="viewport" content="width=device-width,
> initial-scale=1,
> maximum-scale=5">
>
> You need to get into CSS hacking if you want to go further in
> @media based
> CSS formatting, or implementing CSS grids, etc.
>
Apparently, there is a 'responsive' module for Hugo that several
themes use. I'm hoping to find responsiveness out of the box
through careful choice of themes.
>> 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?
>
>
> I think so, as I mentioned earlier, I have used it for a variety
> of sites.
> The Hugo theme tagging system is not great as it relies
> completely on what
> the theme authors manually tag those as. But this[2] gives a
> small
> selection of themes for documentation sites. I might find more
> sites that
> fit your needs as you explore each of the themes on that site
> (don't reply
> 100% on tags).
>
>
>> Or, is the blog focus likely to restrict what I'd like to do?
>>
>
> Hugo Go templating is very powerful[3]. It inherently has no
> restrictions.
> The templating language does not have a "blog focus".
>
> If you decide to use a theme, just as is[*], then that's a
> restriction. I
> would suggest to pick a theme that best fits your need, and then
> gradually
> mold (mould?) it as you learn more of Go templating, to make it
> perfect for
> you.
Perfect. Thanks. I'm looking forward to getting started with
ox-hugo.
Many thanks for the useful links.
All the best,
Tom
> Thanks.
>
> Kaushal
>
>
> [1]:
> https://github.com/jwiegley/use-package/commit/dede56276ce157fb55f84562b10a70978c34230e#diff-980e09e4bfed99830873c784dfb12a7a
>
> [2]: https://themes.gohugo.io/tags/documentation/
>
> [3]: Here are some of the professional non-blog sites created
> using Hugo:
> https://gohugo.io/showcase/.
>
> [*]: Being Emacs users, I doubt if the "use the theme as is"
> would work for
> any of us ;-)
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2018-05-04 15:07 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
2018-05-04 15:07 ` Thomas S. Dye [this message]
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=87y3gzbgtl.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).