Work Your Own Way With Crafter CMS (Series Part 1): Step-Through Debugging

See the original posting on DZone Python

Most CMS platforms do a decent job of simplifying content and digital experience creation and editing for non-technical content managers. The challenges really start once you need to innovate and development is required. Traditionally CMS platforms have been pretty bad for developers. They require a lot of CMS specific knowledge and don’t integrate with developer tools and process.
Here are 7 things that developers really want with a CMS:

  1. Let me work locally with my own tools like my IDE and my source code management.
  2. Let me leverage my existing skills. I want a low learning curve. Don’t make me learn a new, niche framework.
  3. Let me work in teams on multiple projects at the same time without interfering.
  4. Let me maintain a real development process.
  5. Make the integration with the CMS seamless.
  6. Don’t make me do builds.
  7. Don’t make me do heavy deployments.

In this installment of the Work Your Way Series, we’re going to tackle item #1: Let me work locally with my own tools like my IDE and my source code management. Let’s start with some background: Crafter CMS uses Git as its primary content store. That’s the foundation of the solution for developer desire #1. A developer can mount a local clone of a Crafter CMS project directly with their IntelliJ, Netbeans, Eclipse or other IDE. That means they can use their preferred development tools to edit and debug code and templates. And as they work, all of the changes they make are tracked by the Crafter CMS via its native Git support. Sounds awesome right? Let’s learn how to get set up.