Welcome to Jekyll! Updated!
After years of using Drupal 7.x on my personal website, from timothyae.com, to using a secure protocol, and to timothy.sh, I have finally decided, after serveral months of searches, to move to Jekyll for my own website, just to save paid cloud servers fees, among others.
The following are “the” reasons for my switch:
Unlike Drupal, Jekyll pages are static html pages. There’s no need for sql servers, and other server fine tunings.
Ease of management.
When in Drupal, we learned to add nodes and pages, first through its UI. Later on, I decided to automate nodes/pages creation with some tools outside Drupal.
TLTR; I create Drupal nodes via a plain text editor using markdown.
With Jekyll, it’s the default.
When in Drupal, I did custom continuous deployment with my own cloud server, custom made git hooks, bash, features, among others.
While Github pages is free, HTTPS is not supported for Github Pages using custom domain names.
I have seen the advantage of using SSL certificates to my domain names, and this is one of the main factors for the switch.
I’m using Netlify.
The repository, is hosted in Github.
Each time I update my repository, a build is triggered in Netlify and then my site is built.
You’ll find this post in your
_posts directory. Go ahead and edit it and re-build the site to see your changes. You can rebuild the site in many different ways, but the most common way is to run
jekyll serve, which launches a web server and auto-regenerates your site when a file is updated.
To add new posts, simply add a file in the
_posts directory that follows the convention
YYYY-MM-DD-name-of-post.ext and includes the necessary front matter. Take a look at the source for this post to get an idea about how it works.
Jekyll also offers powerful support for code snippets:
Check out the Jekyll docs for more info on how to get the most out of Jekyll. File all bugs/feature requests at Jekyll’s GitHub repo. If you have questions, you can ask them on Jekyll’s dedicated Help repository.