![]() Unfortunately, Jekyll is not officially supported on Windows. The design was based upon a free template from HTML5UP (because you don't want to see what this would look like if I designed it myself). You can pull the full source of the example (plus alternatives built using other static site engines) on GitHub.Īll the character data, content and images used in the sample are from the Adventure Time! wiki. Data sets - the ability to add content that is not a post or page, but rather a custom data type (in the case of this sample that is the character data). ![]() Custom post metadata - the ability to set custom metadata on a per post basis that can be accessed when listing the post or in the display of the post itself.Custom global metadata - the ability to set custom metadata global to the site that can be accessed and utlized in templates.While the site is intentionally simple for example purposes, it offers the opportunity to explore a number of important features beyond the basics of templating and content creation: You can see a glimpse of what the sample looks like below: I'm a fan of the Cartoon Network show Adventure Time! The sample site we'll use is essentially a very simple Adventure Time! fan site. In this article, we'll look at how to get started using Jekyll and build a simple site with it. It was created by Tom Preston-Werner, founder and former CEO of GitHub, and is the engine frequently used for running GitHub Pages. Probably the most popular static site engine is Jekyll. Paired with the growth in services that can add the necessary dynamic pieces to the site (like comments, forms, etc.), static sites have become a viable solution for a large number of sites, especially those that are content-focused. This allows the site to be built dynamically but deployed statically. They make it relatively easy to add and update content, relying on files to store content and data as opposed to databases. The static site engines of today sit somewhere in between the manual updating of the early web and the content management systems that often replaced them. This was fine for very simple sites, but could be painful to manage for large sites. Creating new pages was often a matter of copying an existing HTML file and modifying it. We built our sites with Dreamweaver or Homesite (or -gasp!- FrontPage) and manually updated them to add new content. Once upon a time, the web was mostly static sites.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |