summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorPaul Buetow <paul@buetow.org>2022-11-19 10:52:17 +0000
committerPaul Buetow <paul@buetow.org>2022-11-19 10:52:17 +0000
commite9044cd87daabcb83522a68732e0b96189baf854 (patch)
tree51dbab3bfb80cf84afcb71bd290a942269ca11af /README.md
parentda8db7e2886b9604d7a543be681005b6e146ff63 (diff)
add DRAFT feature
Diffstat (limited to 'README.md')
-rw-r--r--README.md4
1 files changed, 4 insertions, 0 deletions
diff --git a/README.md b/README.md
index 8b744c7..663fab4 100644
--- a/README.md
+++ b/README.md
@@ -91,6 +91,10 @@ Once all of that is done, the `gemtexter` script will convert the new post (plus
You can also have a look at `$BASE_CONTENT_DIR/meta/gemfeed`. There is a metafile for each blog post stored. These metafiles are required for the generation of the Atom feed. You can edit these metafiles manually and run `./gemtexter --generate` or `./gemtexter --feed` again if you want to change some of the Atom feed content.
+## Drafting a blog post before publishing it
+
+If you don't want to publish your article yet (e.g. don't advertise it on the Gemfeed and Atom feed yet), you can draft your article in `./gemtext/gemfeed/DRAFT-article-title-dash-separated.gmi`. Gemtexter will still generate all output formats of the draft, but your site visitors won't be aware of it. Once you want to publish your draft just rename `DRAFT` with the publishing date `YYYY-MM-DD` and from there everything works normally.
+
## Ready to be published
After running `./gemtexter --generate`, you will have all static files ready to be published. But before you do that, you could preview the content with `firefox ../foo.zone-content/html/index.html` or `glow ../foo.zone-content/md/index.md` (you get the idea).