From b3583a4236cae37f38f5d04ab8ff274335715cdf Mon Sep 17 00:00:00 2001 From: Parker Moore Date: Fri, 3 Jun 2016 16:41:35 -0700 Subject: [PATCH] werdz --- ...update-on-jekyll-s-google-summer-of-code-projects.markdown | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/site/_posts/2016-06-03-update-on-jekyll-s-google-summer-of-code-projects.markdown b/site/_posts/2016-06-03-update-on-jekyll-s-google-summer-of-code-projects.markdown index f2407cb6..0f4ce2de 100644 --- a/site/_posts/2016-06-03-update-on-jekyll-s-google-summer-of-code-projects.markdown +++ b/site/_posts/2016-06-03-update-on-jekyll-s-google-summer-of-code-projects.markdown @@ -8,9 +8,7 @@ categories: [community] This year, Jekyll applied to be a part of [Google Summer of Code](https://summerofcode.withgoogle.com/how-it-works/). Students were able to propose any project related to Jekyll. With a gracious sponsorship from GitHub and the participation of myself, @benbalter and @jldec, Jekyll was able to accept two students for the 2016 season, @mertkahyaoglu and @rush-skills. -These students are working on a project that fills a huge need for the community: **a graphical solution for managing your site's content.** - -Current plans include a fully-integrated admin which spins up when you run `jekyll serve` and a web interface at an address like `http://localhost:4000/admin/`. The server implements a common interface which would make a hosted version to make updates to hosted content like a repository on GitHub very easy to write – simply implement the CRUD API and the web interface will happily use that instead. +These students are working on a project that fills a huge need for the community: _a graphical solution for managing your site's content._ Current plans include a fully-integrated admin which spins up when you run jekyll serve and provides a friendly web interface for creating and editing your content. The server and web interface will speak a common HTTP interface so either piece could be switched out for, e.g. a server which writes directly to a repository on GitHub. The strength of text files as the storage medium for content has been part of Jekyll's success. [Our homepage](/) lauds the absence of a traditional SQL database when using Jekyll – your content should be what demands your time, not pesky database downtime. Unfortunately, understanding of the structure of a Jekyll site takes some work, enough that for some users, it's prohibitive to using Jekyll to accomplish their publishing goals.