From f7d892e7cee09ce4e518a5f651bb60c9e5014842 Mon Sep 17 00:00:00 2001 From: David Todd Date: Mon, 27 May 2019 17:09:45 -0500 Subject: [PATCH] Add instructions for posting --- readme.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/readme.md b/readme.md index 73e40f1..507af71 100644 --- a/readme.md +++ b/readme.md @@ -18,6 +18,22 @@ There's not really a whole lot here, but it contains all the configuration files 1. `cd c0de.dev-blog` 1. `make update` + +## Making new posts + +For seperation, I store the content in a private repo (can't read my drafts and encrypted blogs without the password). Also as a matter of choice, I'm using [Markdown](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet) as markup language. + +Categories are defined per folder in the [c0de.dev-content](https://github.com/alopexc0de/c0de.dev-content) repository. To create a new category, simply create a new folder in that repo with at least one post within. For posts without a category, simply throw the new posts in the root of the repo. + +When a new post has been created (with the appropiate [metadata](https://docs.getpelican.com/en/3.6.3/content.html#file-metadata)), the steps to generate the output is as follows: + +1. SSH into your server +1. `cd c0de.dev-blog` +1. Update all submodules (installs new plugins too) - `make update` +1. `cd pelican` +1. Clear the output cache if themes or globals changed - `make clean` +1. Generate the new static HTML site - `make html` + ## TODO * Service/Unit to run this in a server on prod