#Handlebars codekit generator

If you are interested, however, I would definitely recommend systems like Statamic and Kirby over ones like Jekyll and Middleman (both are flat-file based but provide admin UIs). Additionally they have limited URL structures (there are things they can't accomplish with regard to search or filtering results based on the URL). Static site generators are great for developers, but typically not for clients. Remember years ago when every designers' portfolio site was a sprawling WordPress/Drupal/Joomla/PHP Nuke/Mambo/kill-me-now mess? Every post was a database entry in a MySQL database you had no idea how anything really worked and FOR THE LOVE OF GOD ALL YOU WANTED TO DO WAS LOOP OVER SOME IMAGES? Jekyll solves that there's no need for a CMS for that junk.

The caveat is the death of CMSs for small, personal sites for technical owners. I'd keep an eye on Ghost and Buckets - I don't think the CMS is dead, just that the incumbents are shitshows.

#Handlebars codekit generator

I don't think Jekyll is great because it's a static site generator - it's great because it has a sane API, where the alternatives have mindnumbingly awful APIs. Things like Prose.io are cool but they still don't tell the whole story - they're great for editing text but CMS's aren't just about editing text - they're about reviewing drafts and installing plugins and doing adminy stuff - letting people feel like they're in control. Jekyll is fantastic but obviously it's not perfect for non-technical users. I really don't know the answer, but I want to kill myself working with WordPress or Drupal - so whilst the client might enjoy the editing interface, they won't be getting a website to edit because they won't have a web designer by that point. Hopefully it helps you get a lay of the land, and maybe figure out where you want to focus as well.A better CMS, I think. This graphic was part of a process IвЂ™ve gone through to do what I believe is required of any modern front-end developer: determine what youвЂ™re passionate about, determine where your strengths lie, and then focus on the crossover areas. Back-end stuff is included because while technically not front-end, these are items front-end devs must have some familiarity with and will most definitely encounter. The responsible web design category is included because itвЂ™s a category that often gets overlooked, but I feel is incredibly important for modern front-end developers to have minimally an awareness of.

Theories like вЂњresponsive web designвЂќ and back end tools like Rails appear in the spectrum. You may also notice a few items you consider odd. I think they (and many others), donвЂ™t quite fit into the front-end spectrum. IвЂ™ve left a lot out, notably mobile tools I use like Cordova, Rails gems like Spree that are heavily integrated into projects IвЂ™ve worked on, or other tech IвЂ™ve worked with like Electron and native iOS app development. This is a very high-level view of the modern front-end landscape. For now, IвЂ™ll simply list what each piece is (in case itвЂ™s not apparent from the logo): IвЂ™ve written about the details before, so check out those posts for more detail. The sausage can be made in oh so many ways.