From: Martin Steffen <msteffen@ifi.uio.no>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: An Org-mode-based blogging engine?
Date: Mon, 08 May 2023 12:36:30 +0200 [thread overview]
Message-ID: <xk923547m7o1.fsf@rijkaard.ifi.uio.no> (raw)
In-Reply-To: <877ctj1bnr.fsf@mbork.pl> (Marcin Borkowski's message of "Mon, 8 May 2023 10:15:52 +0200")
Hi,
>>>>> "Marcin" == Marcin Borkowski <mbork@mbork.pl> writes:
Marcin> fully Org-mode-based workflow. Ideally, I'd like to be able
Marcin> to do everything - including publishing the posts - from
Marcin> within Emacs.
I use webpage generation (including blogs) using Jekyll. Since I wanted
to stick to org, all is set-up in a way, that the ``content'' including
the blogs is done in org, and then do ``org-publish'' to generate stuff
as fit for consumption for jekyll and the workflow then continues from
there (basically just invoking jekyll to ``publish'' the stuff). jekyll
expects its content in md, but I feel more comfortable with org.
That leads to a two stage thing: first translate org to md (by an
appropriate org-publish set-up) and then generate the web-page from the
md-files. So it's not all org-workflow, but once it's set-up, it's
basically only org as far as content is concerned.
Fine points apply, as jekyll has a lot of moving parts and
configurations. And possible pictures and graphics etc. is also not ``in
org''- And actually, the org-files I am using have some jekyll-specific
md-prefix between
+begin_export markdown
+end_export
to tweak things for jekyll. But the org-part is easy, and for me it
works smooth.
In a different response, HUGO was mentioned. I don't have experience
with HUGO, but it's probably comparable to jekyll.
Martin
Marcin> I know about things like "Org publish" and ox-hugo, though I
Marcin> never used them - and there are probably others - but I'm
Marcin> asking specifically about two things:
Marcin> A. other people's experiences with similar workflows, and
Marcin> B. tool/workflow recommendations.
Marcin> Here are my requirements, in no particular order.
Marcin> 1. I want the blog to be fully static HTML+CSS, with a tiny
Marcin> sprinkling of (my custom) JS.
Marcin> 2. I want to publish a whole set of HTML files from a single
Marcin> Org mode file. I will need to preserve internal links (so
Marcin> that I can link to another headline and the result will be
Marcin> one post linking to another), and of course I will need
Marcin> external links. The blog will live on some server I will
Marcin> have ssh access to, so for publishing it should be enough to
Marcin> scp some files somewhere.
Marcin> 3. I want to be able to fully customize the HTML produced.
Marcin> I want it to be as simple as possible (but see below). I
Marcin> will also need it to be put in some kind of a template, so
Marcin> that every page will contain things like a header, footer
Marcin> and a sidebar.
Marcin> 4. I am going, though, to need some custom "blocks" - in
Marcin> HTML parlance, <div>s and possibly also <span>s. I want to
Marcin> be able to mark them up somehow in my Org source and get
Marcin> <div class="..."> and <span class="...">. Reusing existing
Marcin> markup (like _underline_, which I'm not going to use) is not
Marcin> enough - I will need more than a dozen of those custom
Marcin> classes.
Marcin> Any thought, suggestions, recommendations?
Marcin> -- Marcin Borkowski http://mbork.pl
next prev parent reply other threads:[~2023-05-08 10:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 8:15 An Org-mode-based blogging engine? Marcin Borkowski
2023-05-08 8:22 ` Ruijie Yu via General discussions about Org-mode.
2023-05-08 8:30 ` Ihor Radchenko
2023-05-20 7:30 ` Marcin Borkowski
2023-05-08 10:36 ` Martin Steffen [this message]
2023-05-20 7:32 ` Marcin Borkowski
2023-05-08 10:44 ` Dr. Arne Babenhauserheide
2023-05-20 7:34 ` Marcin Borkowski
2023-05-08 15:48 ` Vinícius Moraes
2023-05-20 7:37 ` Marcin Borkowski
2023-05-20 10:49 ` Max Nikulin
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=xk923547m7o1.fsf@rijkaard.ifi.uio.no \
--to=msteffen@ifi.uio.no \
--cc=emacs-orgmode@gnu.org \
--cc=mbork@mbork.pl \
/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).