Skip to content

Commit 28e4ac8

Browse files
committed
Goodbye Wordpress, hello Github (Jekyll)
1 parent a3648ba commit 28e4ac8

File tree

2 files changed

+70
-17
lines changed

2 files changed

+70
-17
lines changed

_drafts/goodbye-worpdress-hello-github-jekyll.md

Lines changed: 0 additions & 17 deletions
This file was deleted.
Lines changed: 70 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,70 @@
1+
---
2+
title: Goodbye Wordpress, hello Github (Jekyll)
3+
categories:
4+
- personal
5+
- english
6+
tags:
7+
- blog
8+
- jekyll
9+
- wordpress
10+
---
11+
12+
It has been a while I'm not writing in this blog. I have my reasons but the
13+
main one is because I've been busy migrating the whole website from
14+
[Wordpress](https://wordpress.org) to Github (time ago [I also moved my CV on
15+
Github]({{ site.url }}/2015/03/27/my-cv-on-github/)). To be more precise I
16+
moved to [Github Pages](https://pages.github.com).
17+
18+
With Github pages you can set up a website for every project you have on Github
19+
or you can set up a "personal" website (linked to your *username.github.io*
20+
repository on Github).
21+
22+
The underlying technology is [Jekyll](https://jekyllrb.com) (yes, written in
23+
Ruby... :-/).
24+
You need to install it on your computer is you are migrating an existent
25+
website to Jekyll or if you want to customise your website even more.
26+
The reasons I move to Github Pages are summed in the following video
27+
28+
{% include video id="2MsN8gpT6jY" provider="youtube" %}
29+
30+
The old website was composed from:
31+
* digitalocean.com server, which I strongly suggest
32+
([grab my referral!](https://m.do.co/c/a9ba99ae5c7c))
33+
* Wordpress installation (theme and software updates)
34+
* Mysql installation (backups, data restore, schema upgrades, etc...)
35+
* scripting around maintenance
36+
37+
The overhead for a simple website was simply too much: software updates and
38+
upgrades, schema migrations, backups, data restores, dying processes,
39+
dying processes and many other tasks which were time consuming.
40+
41+
The new website is composed from:
42+
* git repository *(yes, that's right!)* :)
43+
44+
No databases, no schemas, no servers, no passwords, no hacks, no software
45+
updates, no dying processes, no downtime (well there might be, but Github will
46+
fix it for me) and **backups are already included!**
47+
48+
So if you already use Github, **wait no more!** Set up your website now!
49+
50+
If you want to migrate your existent website to Jekyll... Well, **good luck!** :)
51+
Joking apart, the process might not be so straightforward as a lot of things
52+
need to be ported/configured:
53+
54+
* **posts and pages**: Jekyll is blog aware so you can export to it from the
55+
majority of blog softwares ([check it here](http://import.jekyllrb.com)).
56+
Although my blog was on Wordpress **this took me plenty of time** as now always
57+
the export works as expected. I've used both scripts and manual work to do a
58+
proper migration
59+
* **comments**: as there is no database you need to use an external service.
60+
I've chosen [DISQUS](https://disqus.com)
61+
* **URLs**: I've mapped as much as I could the old URLs with the new ones
62+
* **theme**: I went for [Minimal Mistakes](https://mmistakes.github.io/minimal-mistakes/)
63+
as the documentation is just excellent and I love the clean design!
64+
* **custom code**: depends how many plug-ins you used in your previous platform,
65+
you might end up in writing plenty of custom code to keep the same
66+
functionalities
67+
68+
Well, if you have any question I bet you can find my contact or comment this post
69+
70+
**Blogging with `VIM` and publishing with `git push` is just priceless! :)**

0 commit comments

Comments
 (0)