From 03c2811ae01d6e6b7fefc3c70b900b0ab82b4a69 Mon Sep 17 00:00:00 2001 From: Parker Moore Date: Fri, 3 Jun 2016 14:58:51 -0700 Subject: [PATCH] Use jekyll-mentions and restructure --- Gemfile | 1 + site/_config.yml | 1 + ...date-on-jekyll-s-google-summer-of-code-projects.markdown | 6 ++++-- 3 files changed, 6 insertions(+), 2 deletions(-) diff --git a/Gemfile b/Gemfile index 54983415..253826aa 100644 --- a/Gemfile +++ b/Gemfile @@ -86,4 +86,5 @@ group :site do gem "jekyll-sitemap" gem "jekyll-seo-tag", "~> 1.1" gem "jekyll-avatar" + gem "jekyll-mentions" end diff --git a/site/_config.yml b/site/_config.yml index e284a81b..0b69dc98 100644 --- a/site/_config.yml +++ b/site/_config.yml @@ -32,3 +32,4 @@ gems: - jekyll-sitemap - jekyll-seo-tag - jekyll-avatar + - jekyll-mentions 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 db19662c..f2407cb6 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 @@ -6,9 +6,11 @@ author: parkr 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](https://github.com/benbalter) and [@jldec](https://github.com/jldec), Jekyll was able to accept two students for the 2016 season, [@mertkahyaoglu](https://github.com/mertkahyaoglu) and [@rush-skills](https://github.com/rush-skills). +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 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. 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.