emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Jud Taylor <jud.taylor@protonmail.com>
To: "Emacs-orgmode@gnu.org" <Emacs-orgmode@gnu.org>
Subject: Questions after Attempt at using org-publish per https://orgmode.org/worg/org-tutorials/org-publish-html-tutorial.html
Date: Sun, 14 Oct 2018 01:55:59 +0000	[thread overview]
Message-ID: <G2_ZEoCnqoqfO8aPDaxx2uxopYCSQiKowHxIE7OKqY-qo5KGmCuJZ6op2Z0NlHyw82GI2JvCKvaZ6vX32i0W-Ph5R0pUoN5dSZaHZgA-cq0=@protonmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 961 bytes --]

I have some questions about how to use ox-publish to create static sites.

I have followed steps documented at https://orgmode.org/worg/org-tutorials/org-publish-html-tutorial.html.

I have documented my steps and copied source and output at https://github.com/gptix/org-site-test

I have tried to search for answers on the emacs-orgmode mailing list, and on the web.

My three current issues:

- I do not understand how css info is being injected into output html files. I did not create any css file to be referenced, but styling is being included as CDATA.

- I do not understand what the
:auto-preamble t
in a component is for.

- I do not understand the relation between
(require 'ox-publish)
at the beginning of the tutorial, and
(require 'org-publish)
in the portion of the tutorial describing how to actually publish.

I'd love any help or a pointer to where I can read about these.

Thanks.

Sent with [ProtonMail](https://protonmail.com) Secure Email.

[-- Attachment #2: Type: text/html, Size: 1607 bytes --]

next             reply	other threads:[~2018-10-14  1:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-14  1:55 Jud Taylor [this message]
2018-11-05  0:43 ` Questions after Attempt at using org-publish per https://orgmode.org/worg/org-tutorials/org-publish-html-tutorial.html Jud Taylor

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='G2_ZEoCnqoqfO8aPDaxx2uxopYCSQiKowHxIE7OKqY-qo5KGmCuJZ6op2Z0NlHyw82GI2JvCKvaZ6vX32i0W-Ph5R0pUoN5dSZaHZgA-cq0=@protonmail.com' \
    --to=jud.taylor@protonmail.com \
    --cc=Emacs-orgmode@gnu.org \
    /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

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).