From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kaushal Modi Subject: Re: Moving from Jekyll to Orgmode Date: Fri, 04 May 2018 13:43:38 +0000 Message-ID: References: <1524949519.21032.171.camel@gmail.com> <874ljump59.fsf@atmarama.com> <02CE4F97-08E0-4A50-9CE5-68D0D7712ACD@zzamboni.org> <87zi1fykxa.fsf@tsdye.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000007f6bc8056b618285" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47548) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fEb04-0006QL-UA for emacs-orgmode@gnu.org; Fri, 04 May 2018 09:43:55 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fEb03-0004LK-8b for emacs-orgmode@gnu.org; Fri, 04 May 2018 09:43:52 -0400 Received: from mail-lf0-x22e.google.com ([2a00:1450:4010:c07::22e]:33664) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fEb02-0004Js-RJ for emacs-orgmode@gnu.org; Fri, 04 May 2018 09:43:51 -0400 Received: by mail-lf0-x22e.google.com with SMTP id m18-v6so31026367lfb.0 for ; Fri, 04 May 2018 06:43:50 -0700 (PDT) In-Reply-To: <87zi1fykxa.fsf@tsdye.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: "Thomas S. Dye" Cc: Luis Roca , Diego Zamboni , emacs-orgmode@gnu.org --0000000000007f6bc8056b618285 Content-Type: text/plain; charset="UTF-8" Hello Thomas, On Fri, May 4, 2018 at 2:50 AM Thomas S. Dye 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? > 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: You need to get into CSS hacking if you want to go further in @media based CSS formatting, or implementing CSS grids, etc. > 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. 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 ;-) -- Kaushal Modi --0000000000007f6bc8056b618285 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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 pa= st (and it worked ;-)).
=C2=A0
=C2=A0 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 #+hu= go_base_dir keyword and EXPORT_FILE_NAME property (if using per-subtree flo= w). So it should not be too difficult. To get an idea, I made these[1] chan= ges to make the pre-existing use-package Org manual ready for ox-hugo expor= t.
=C2=A0
I'm especially keen on previewing the web pages as I work on them,
which was super easy to set up (thanks!),

G= reat! So I gather that you were able to get a preliminary setup of ox-hugo= =C2=A0+ Hugo working?
=C2=A0
an= d generating=C2=A0 "responsive" content to satisfy my smartphone = connected students.

That part is not to= o difficult if you want to get the basic responsiveness.. just adding the v= iewport meta tag in HTML head does most of the job:

<meta name=3D"viewport" content=3D"width=3Ddevice-w= idth, initial-scale=3D1, maximum-scale=3D5">

You need to get into CSS hacki= ng if you want to go further in @media based CSS formatting, or implementin= g CSS grids, etc.
=C2=A0
I see that ox-hugo and many Hugo templates have a blog as their
focus.=C2=A0 Is it reasonable to go down the ox-hugo path for my
planned sites?

I think so, as I mentioned e= arlier, I have used it for a variety of sites. The Hugo theme tagging syste= m is not great as it relies completely on what the theme authors manually t= ag those as. But this[2] gives a small selection of themes for documentatio= n 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).
=C2= =A0
=C2=A0 Or, is the blog focus likely= to restrict what I'd like to do?

H= ugo Go templating is very powerful[3]. It inherently has no restrictions. T= he templating language does not have a "blog focus".

If yo= u decide to use a theme, just as is[*], then that's a restriction. I wo= uld suggest to pick a theme that best fits your need, and then gradually mo= ld (mould?) it as you learn more of Go templating, to make it perfect for y= ou.

Thanks.

Kaushal

[3]: Here are some of the professiona= l 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 ;= -)
--

Kaushal Modi

--0000000000007f6bc8056b618285--