1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
|
#+STARTUP: showall
* [[https://orgmode.org/manual/Publishing.html][Publishing]]
Org includes a publishing management system that allows you to configure
automatic HTML conversion of /projects/ composed of interlinked Org files. You
can also configure Org to automatically upload your exported HTML pages and
related attachments, such as images and source code files, to a web server.
You can also use Org to convert files into PDF, or even combine HTML and PDF
conversion so that files are available in both formats on the server.
Publishing has been contributed to Org by David O’Toole.
** [[https://orgmode.org/manual/Configuration.html][Configuration]]
Publishing needs significant configuration to specify files, destination and
many other properties of a project.
#+NAME: www-test-data
#+BEGIN_SRC elisp :tangle www-test-data.el
;; -*- lexical-binding: t; -*-
( load "~/src/channel/www/build-site" )
( print "publish-test-1" )
( publish :data-projects ( list "test.pl" "example.org" ) )
( print "publish-test-2" )
( publish
:data-projects
( list "test.pl"
:property1
"value1"
:property2
"value2" ) )
( print "publish-test-3" )
( publish "test.pl"
:components
( list "example.pl" "example.org" ) )
#+END_SRC
*** [[https://orgmode.org/manual/Project-alist.html][The variable =org-publish-project-alist=]]
Publishing is configured almost entirely through setting the value of one
variable, called =org-publish-project-alist=. Each element of the list
configures one project, and may be in one of the two following forms:
#+BEGIN_EXAMPLE
( "project-name" :property value :property value ... )
#+END_EXAMPLE
i.e., a well-formed property list with alternating keys and values, or:
#+BEGIN_EXAMPLE
( "project-name" :components ( "project-name" "project-name" ... ) )
#+END_EXAMPLE
In both cases, projects are configured by specifying property values. A project
defines the set of files that are to be published, as well as the publishing
configuration to use when publishing those files. When a project takes the
second form listed above, the individual members of the =:components= property
are taken to be sub-projects, which group together files requiring different
publishing options. When you publish such a “meta-project”, all the components
are also published, in the sequence given.
#+NAME: build-site
#+BEGIN_SRC elisp :tangle build-site.el
;; -*- lexical-binding: t; -*-
( defun publication-object ( )
( let ( ( object-projects ( list ) )
( org-publish-project-alist ( list ) )
( success-report "Build complete!" ) )
( list
:object-compose
( lambda ( )
( setq org-publish-project-alist ( list object-projects ) )
( ) )
:object-get-projects
( lambda ( data-projects )
( setq object-projects ( append data-projects object-projects ) )
( ) )
:object-report
( lambda ( )
( print object-projects )
( print org-publish-project-alist )
( print success-report )
( ) ) ) ) )
( setq publication-instance ( publication-object ) )
( setq object-compose ( plist-get publication-instance :object-compose ) )
( setq object-projects ( plist-get publication-instance :object-get-projects ) )
( setq object-report ( plist-get publication-instance :object-report ) )
( defun publish ( &rest project-data )
( let ( ( data-projects ( plist-get project-data :data-projects ) ) )
( funcall object-projects data-projects )
( funcall object-compose )
( funcall object-report )
( ) ) )
#+END_SRC
* EOF
|
