All geek questions in one place

What is the difference between pelican./content and make html?

I am starting to learn Pelican today because I want to move my blog from wordpress to Pelican.

However, after reading the docs , I still don't know the difference between pelican ./content and make html . They seem to be creating a static website. In addition, pelican ./content always returns UnicodeDecodeError** for me, while pelican. / Content`.

What is the difference between them and why?

+4
source share
2 answers

In the folder where you use $ pelican-quickstart , you will find a file called Makefile .

You will find a line like html: clean $(OUTPUTDIR)/index.html and $(OUTPUTDIR)/%.html: $(PELICAN) $(INPUTDIR) -o $(OUTPUTDIR) -s $(CONFFILE) $(PELICANOPTS) .

This file shows you what the pelican did when you type make *** , and you can configure many other things in this file.

+3
source

pelican ./content starts creating a website using the default settings and tries to guess the location of your content, output, and configuration files.

make html calls pelican , but explicitly gives it an input directory, an output directory, a configuration file, and, optionally, additional options.

Basically, make html (along with make regenerate ) are convenient methods that make your work easier. In any case, you must run make publish to generate content that should be uploaded to your web server, since it uploads publishconf.py files that define several additional parameters (rss feeds) and allow you to change the settings for the “correct” web website.

+2
source

Source: https://habr.com/ru/post/1501652/

More articles:


All Articles