In this series of article we're going to introduce you to the Jekyll static site Content Management System (CMS). Static site generators are different from dynamic site systems like WordPress, Joomla, and Drupal. While dynamic sites are generated based on various types of back-end processing and pulling information from databases, static site systems generate complete HTML files that can be served instantly without any extra processing. </p> <p> Here are some of the benefits you can expect with using a static site CMS: </p> <ul> <li>No databases</li> <li>Requires minimal server specs</li> <li>Lightning speed</li> </ul> <p> Instead of building the site dynamically on page load, Jekyll creates plain HTML files that require no further processing. This means pages are served instantly. </p> <a name="markdown"></a> <h2>Easy Coding with Markdown</h2> <p> When writing your web pages with Jekyll, you don't need to use HTML coding. You can write in the simplified <em>Markdown</em> syntax. </p> <pre> # H1 Heading ## H2 Heading ### H3 Heading (and so forth) Underscores create _emphasis_, and so do *asterisks*. <p>Underscores create <em>emphasis</em>, and so do <em>asterisks</em>.</p> Double those to create __boldness__, and so **forth**. <p>Double those to create <b>boldness</b>, and so <b>forth</b>. </p></pre> <p> Visit the complete <a href="https://daringfireball.net/projects/markdown/">Markdown documentation</a> for detailed syntax usage. </p> <p> It's your choice. Jekyll lets you create pages and blog posts using both the simplified Markdown syntax or straight HTML. </p> <a name="pros-cons"></a> <h2>Pros and Cons for Using Jekyll</h2> <p> As with any CMS, there are benefits and drawbacks to adopting Jekyll as your system. You will need to decide what you need from your website and where your comfort level is. </p> <table class="table table-striped table-bordered" style="text-align:left;"> <tr> <th>Pros</th> <th>Cons</th> </tr> <tr> <td> <ul> <li>No databases</li> <li>Basic server requirements</li> <li>Very fast</li> <li>Improved security</li> </ul> </td> <td> <ul> <li>No server-side admin interface</li> <li>Requires some command line comfort</li> <li>Requires using a text editor (like Notepad or Textmate) instead of your favorite WYSIWYG program (like Microsoft Word)</li> <li>Limited support options (you'll need to visit forums)</li> </ul> </td> </tr> </table> <a name="basic-workflow"></a> <h2>Basic Jekyll Workflow</h2> <p> The basic Jekyll workflow requires installing Jekyll in your local computer. Once that's done, you can work on your site locally until you're happy with it. Then, you can "build" the site using a single command line directive. The site will then be fully contained in a directory of your choosing and you can then upload your site with whichever <a href="/support/website/how-to-manage-files-server/">file management</a> method you prefer. </p> <h2>Final Thoughts</h2> <p> Now you have learned a little bit about the Jekyll CMS and why you might consider using. In the next article in the Jekyll series, we'll show you <a href="/support/website/jekyll/how-to-install-jekyll/">how to install Jekyll</a> on your local computer.