From: Scott Randby <srandby@gmail.com>
To: ST <smntov@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Moving from Jekyll to Orgmode
Date: Sun, 29 Apr 2018 10:45:38 -0400 [thread overview]
Message-ID: <94637a3c-fe08-96ad-68ca-f94628d29a05@gmail.com> (raw)
In-Reply-To: <1524991812.21032.180.camel@gmail.com>
On 04/29/2018 04:50 AM, ST wrote:
> Hi Scott,
>
> thank you, and all other responders, for the shared information. The
> reason I want to leave Jekyll is because I don't want to depend on a
> tool that relies on language (Ruby)/environment that I don't know/use
> (in this respect Hugo is the same for me). I prefer something more
> simplistic, even though if I'll have to invest some time for it to work
> initially. Those 3 features I've mentioned are almost all I need, more
> or less.
>
> Could you, please, share your website publishing workflow (considering
> the 3 issues I've mentioned)?
I'm sorry, but I can't address any of your three issues. My site is in English only, I use regular links, and my style is very simple and made so the site will work well on any device. Here is a link to it: http://srandby.org/
The Org source code isn't available yet, but it isn't anything special. The key is really the CSS which you can easily obtain.
For publishing, I update a file, use Org's HTML export facility (C-c C-e h or C-c C-e C-s h to export a subtree), and then upload to the server. Not very sophisticated, but I find it to be very efficient.
I haven't had time to look into the more complex things one can do regarding Org and websites.
Scott
next prev parent reply other threads:[~2018-04-29 14:45 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 [this message]
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
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=94637a3c-fe08-96ad-68ca-f94628d29a05@gmail.com \
--to=srandby@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=smntov@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).