In order to publish projects consisting of multiple file types I add the following to my .emacs file:
A derived export backend is what you want. Here's an example where I've created a derived backend that changes the main html template.
In org-export-define-derived-backend you provide an alist with the parts of the backend you want to override.
In my backend I only wanted to replace the top level template.
(org-export-define-derived-backend 'pd-html 'html
The :exclude property should do the trick.
I think the reason the property is not working for you is because its value should form a regular expression, whereas your example is a glob pattern.
Try using :exclude ".*/private/.*" or similar.
See also the GNU Emacs Manual node on Regular Expressions for the particularities of its syntax.
This was non-obvious and the scenario of single/select files wasn't mentioned in any documentation specifically, so here's my solution: (only the last two lines are relevant)
Have a look at some of the HTML-derived exporter backends, for example https://github.com/yyr/org-mode/blob/master/contrib/lisp/ox-rss.el#L114.
This uses org-export-define-derived-backend to customize how the HTML backend processes org files:
(org-export-define-derived-backend 'rss 'html
'(?r "Export to RSS"
((?R "As RSS buffer"
Images can be exported as Inline in two styles: with hyperlink or without hyperlink.
Inline With Hyperlink
Note that it is mandatory to put a prefix like file: or http: in the Description portion ([file:./image_thumbnail.png]) of the above image link; otherwise ox-html will export that as a text hyperlink ...
You misinterpreted the meaning of the first argument of org-publish-org-to.
It is the export backend and not a function. Because of the special structure of the pandoc backend replacing org-pandoc-export-to-html with 'pandoc does not work. If you do that you only get the filtered org stuff in your output files. The final translation to html is missing. (That ...
I use this method to create code examples to write How To Use org-mode documentation.
Wrap Code Blocks within a New org Code Block
Use C-c C-v d to create empty org code block then add #+NAME: and :exports code headers to code block.
#+begin_src org :exports code
Edit org block.
Important: Click ...
The solution I found was to write my own publishing function. The function is a wrapper around the org-latex-publish-to-pdf that also calls rename-file.
(defun publish-function-counselor-appointments (PLIST FILENAME PUB-DIR)
(org-latex-publish-to-pdf PLIST FILENAME PUB-DIR)
(rename-file "~/appointments.pdf" "~/counselor_appointments.pdf"))
Maybe you should redefine this function like this:
(defun org-wiki--org-link (path desc backend)
"Creates an html org-wiki pages when exporting to html.
Example: The hyperlink [[wiki:Linux][Dealing with Linux]]
will be exported to <a href='Linux.html'>Dealing with Linux</a>"
I am thinking about the same thing.
I think the issue is that org-reveal-export-to-html is not a defined publishing function.
There is a nice solution provided by Matt Price and it works on my system as well.
Here it is:
Define a publishing function that connects reveal to org-publish.
(defun mwp-org-reveal-publish-to-html (plist filename pub-dir)
This is going to be a long post, so bear with me. The only Emacs way I see so far is to use .dir-locals.el and keep it relatively clean so you don't have to approve evals every time you change something. Presumably you trust your repos:-) The rest is to give you an idea... from newb to newbs.
(eval . (my-mega-project-setup))
You got to ...
According to the description of (org-publish) function:
(org-publish PROJECT &optional FORCE ASYNC)
PROJECT is either a project name, as a string, or a project
alist (see `org-publish-project-alist' variable).
So I created an emacs-lisp-script following this scheme:
I have written two org-mode exporter for pelican and hexo for my self (no public release yet, just opensource on GitHub)
In your case, the best way is write a org-mode exporter based on ox-html, I don't know if anyone did it for jekyll but you can based on my org-hexo to achieved this.
The details are in the org-mode manual but I missed it. Basically you need to ensure you don't add a title. So:
#+ATTR_HTML: :alt Architectural overview :style border:none;