Jekyll VS Craft CMS

Jekyll Reviews

Craft CMS Reviews

Jekyll mentions (180)

• Creating excerpts in Astro

  This blog is running on Hugo. It had previously been running on Jekyll. Both these SSGs ship with the ability to create excerpts from your markdown content in 1 line or thereabouts. - Source: dev.to / about 2 months ago

• JS Toolbox 2024: Essential Picks for Modern Developers Series Overview

  We also take a look into static site generators, covering Astro, Nuxt, Hugo, Gatsby, and Jekyll. We take a detailed look into their usability, performance, and community support. - Source: dev.to / 2 months ago

• Starlight vs. Docusaurus for building documentation

  In that case, what we need would be closer to a static site generator (like Gatsby, Hugo, Jekyll). But, static site generators aren't the best choice either because we would have to build a lot of documentation-focused functionality (like versioning, search, and code blocks) ourselves. - Source: dev.to / 3 months ago

• Ask HN: Looking for lightweight personal blogging platform

  In future, if you want to move from Jekyll to something else, you just have to worry about that `_posts` and `_assets` folder. They may have different naming convention but you can just config-managed it or change it to your choice. This is why I suggested owning that two yourself. You also may not worry about FrontMatter[3] (meta in the header) and its accompanying jazz by asking Jekyll to use the plugins... - Source: Hacker News / 3 months ago

• Ask HN: Looking for lightweight personal blogging platform

  As per many other comments, it sounds like a static site generator like Hugo (https://gohugo.io/) or Jekyll (https://jekyllrb.com/), hosted on GitHub Pages (https://pages.github.com/) or GitLab Pages (https://about.gitlab.com/stages-devops-lifecycle/pages/), would be a good match. If you set up GitHub Actions or GitLab CI/CD to do the build and deploy (see e.g.... - Source: Hacker News / 3 months ago

Craft CMS mentions (31)

• Different flavors of content management

  The most typical approach is having a CMS admin panel sit somewhere on the server; everyone with an account uses this. This is a very convenient approach, especially when working with a team. This way, many people can work on different articles simultaneously without worrying about potential conflicts or overwriting stuff. The only con is related to security - everyone can try to get inside, and if you forget to... - Source: dev.to / 8 months ago

• Go with PHP

  PHP has a lot of top tier CMSes. IMHO bunch of them are even better than Statamic. Craft CMS (https://craftcms.com/) is a lot more mature database based CMS. Kirby (https://getkirby.com/) is better at flat-file and has a lot better admin interface. Twill (https://twillcms.com/) is better integrated in Laravel and is fully open-source. Statamic mostly feels like it's sitting besides Laravel and they call themselves... - Source: Hacker News / 12 months ago

• Stack to build and deploy a fully functional personal blog?

  You're basically looking for any CMS that supports headless mode. E.g. Strapi (https://strapi.io/, NodeJS based), CraftCMS (https://craftcms.com/, PHP based) or countless others. Source: 12 months ago

• A mate of mine built a cool little Tottenham Database showing the history of spurs.

  It's built on Craft CMS. Makes the relationships between elements (a match and a player, for example) super easy. Source: about 1 year ago

• Creating a CMS with React, what should I look at?

  Is there a reason you aren’t using an existing CMS? There’s a lot that provide all the UI functionality you are talking about and then expose it via a API to be consumed in your front end. https://craftcms.com is one option I’ve had good success with. Source: over 1 year ago