1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
|
#lang scribble/manual
@; SPDX-License-Identifier: BlueOak-1.0.0
@; This file is licensed under the Blue Oak Model License 1.0.0.
@(require "scribble-helpers.rkt")
@(require (for-label racket/base "../pollen.rkt"))
@section{How I Publish: A Quick Tour}
This isn’t a tutorial, since these steps probably won’t all work on your computer. Think of these
narrations like me talking while I drive.
@subsection{Creating an article}
Open a terminal window.
@terminal{@cmd{> cd /path/to/thelocalyarn}}
The @tt{make} command provides a high-level control panel for common tasks. Typing just make from
a terminal window shows a list of options:
|
|
|
|
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
|
#lang scribble/manual
@; SPDX-License-Identifier: BlueOak-1.0.0
@; This file is licensed under the Blue Oak Model License 1.0.0.
@(require "scribble-helpers.rkt")
@(require (for-label racket/base pollen/core "../pollen.rkt"))
@title{How I Publish: A Quick Tour}
This isn’t a tutorial, since these steps probably won’t all work on your computer. Think of these
narrations like me talking while I drive.
@section{Creating an article}
Open a terminal window.
@terminal{@cmd{> cd /path/to/thelocalyarn}}
The @tt{make} command provides a high-level control panel for common tasks. Typing just make from
a terminal window shows a list of options:
|
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
|
Sync done, sent: 10153 received: 4680 ip: 162.243.186.132
}|
As you can see, Fossil does an automatic pull before the commit, and another automatic push
afterwards. This commit is now visible on the public timeline, and the source code for the article
can now be seen on the public repo at @tt{thelocalyarn.com/code/}.
@subsection{Adding notes to an article}
A few days (or years) after doing the above, I receive an email from Marjorie with commenting on
@italic{My New Post} and I decide to publish her comments.
I open the article in my editor and add some lines to the end:
@filebox["articles/my-new-post.poly.pm"
|
|
|
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
|
Sync done, sent: 10153 received: 4680 ip: 162.243.186.132
}|
As you can see, Fossil does an automatic pull before the commit, and another automatic push
afterwards. This commit is now visible on the public timeline, and the source code for the article
can now be seen on the public repo at @tt{thelocalyarn.com/code/}.
@section{Adding notes to an article}
A few days (or years) after doing the above, I receive an email from Marjorie with commenting on
@italic{My New Post} and I decide to publish her comments.
I open the article in my editor and add some lines to the end:
@filebox["articles/my-new-post.poly.pm"
|
125
126
127
128
129
130
131
132
133
134
135
136
|
Now if you open the article’s permlink, you’ll see the note appears in a “Further Notes” section at
the bottom — again, just like a normal blog post comment.
But if you go to the Blog section, you’ll see the note appearing in its own space right alongside
the other articles, as if it were a separate post. It will also appear in a separate entry in the
RSS feed.
@subsection{What’s not here yet}
Eventually there will be facilities for creating PDF files of individual articles, and print-ready
PDFs of books containing collections of articles.
|
|
|
125
126
127
128
129
130
131
132
133
134
135
136
|
Now if you open the article’s permlink, you’ll see the note appears in a “Further Notes” section at
the bottom — again, just like a normal blog post comment.
But if you go to the Blog section, you’ll see the note appearing in its own space right alongside
the other articles, as if it were a separate post. It will also appear in a separate entry in the
RSS feed.
@section{What’s not here yet}
Eventually there will be facilities for creating PDF files of individual articles, and print-ready
PDFs of books containing collections of articles.
|
