paragraph for the jekyll post
This commit is contained in:
parent
e4b2615612
commit
d10ee232e3
|
@ -42,6 +42,14 @@ The ones I'd recommend:
|
|||
- [Digital Garden](https://github.com/maximevaillancourt/digital-garden-jekyll-template) -
|
||||
Excellent for notes instead of a blog, I'm customizing this for a private novel. This template even features a graph showing the relationships between the notes!
|
||||
|
||||
### Insane extendability
|
||||
|
||||
As Jekyll is just a generator for static html pages, we can make use of the
|
||||
endless amount of web technologies without worrying how they will play with our
|
||||
backend. Want to use your favorite CSS framework, or even add your own CSS? No
|
||||
problem. Using existing template websites is easy too! Jekyll even has builtin
|
||||
SCSS support, which makes adding your own custom CSS much more comfortable.
|
||||
|
||||
## Cons of Jekyll
|
||||
|
||||
### Multilingual sucks
|
||||
|
@ -56,6 +64,13 @@ seems to be still maintained is [polyglot](https://github.com/untra/polyglot).
|
|||
|
||||
## Deployment with Docker
|
||||
|
||||
**[Docker](https://www.docker.com)** is a really useful service that can be
|
||||
used to deploy many services, Jekyll too. I won't go into the details here,
|
||||
but the idea is that your kernel runs a separate mini OS, which reproduces the
|
||||
same environment every time and streamlines deployment. It's also good for
|
||||
security, as someone who takes over the webserver will only have the rights
|
||||
of the webserver inside the docker container, instead of on your real OS.
|
||||
|
||||
The "official" Jekyll Docker container is unmaintained since 2022, so if you
|
||||
want to deploy Jekyll with docker you need to create your own container. I based
|
||||
this on the standard [ruby image](https://hub.docker.com/_/ruby/).
|
||||
|
|
Loading…
Reference in New Issue