Improving the Accessibility of Jekyll

01 Jul 2017

Due to it’s simplicity, Jekyll offers many advantages over other blogging platforms, including increased loading speeds, securtity, and server–side consistency. In the words of it’s creators,

Jekyll does what you tell it to do – no more, no less. It doesn’t try to outsmart users by making bold assumptions, nor does it burden them with needless complexity and configuration. Put simply, Jekyll gets out of your way and allows you to concentrate on what truly matters: your content.

Also, for those in a hurry to get their blog up and running, the Jekyll community has also created a large assortment of easily customizable free and paid themes. So no matter your goals, you’re guarenteed to find a theme that suits your needs. Additionally, Jekyll’s integration with GitHub Pages provides users with free web-hosting for each GitHub profile, potentially saving hundreds of dollars in hosting costs for blogs with high traffic.

So why does this platform seem isolated to the developer community?

A major aspect of Jekyll is that it uses markdown for writing and formatting blog posts. For most developers, writing in markdown quickly becomes second nature from writing project documentation on GitHub or similar version control repository sites. Though, for the less technically–inclined, this foreign markup can be intimidating at first glance, consequently turning off many potential users.

In response, I’ve began development of Hyde, a Jekyll–inspired markdown editor that aims to improve the accessibility of writing blog posts in markdown by providing an experience that’s akin to writing in a word processor or online text formatting field, while still exposing users to the markdown syntax. Although still in it’s infancy, Hyde currently features a formatting toolbar, side–by–side HTML and rendered Markdown live–preview, sync–scrolling, as well as syntax–highlighting for markdown and GFM–compatible HTML with a collection of syntax themes. Additionally, through future developments, I hope to also incorporate automated YAML front-matter creation, git-integration, and many more features.

If you are a current or prospective Jekyll user that’s interested in this project, feel free to share any suggestions or features you’d like to see in the future via Github or the link below!


Back to Top

Brett Stevenson


Published

Share this post