Basics of Headless CMS

Summary

Building a web application requires integrating a number of separate concerns into a single experience. One of the common requirements is a content management system to allow product owners and marketers to make the changes needed for them to do their jobs. Rather than spend the time and focus of your developers to build the end to end system a growing trend is to use a headless CMS. In this episode Jake Lumetta shares why he decided to spend his time and energy on building a headless CMS as a service, when and why you might want to use one, and how to integrate it into your applications so that you can focus on the rest of your application.

Interview

  • Introductions
  • How did you get introduced to Python?
  • Can you start by describing what a headless CMS is?
    • How does the use case and user experience differ from working with a traditional CMS (e.g. WordPress, etc.)?
    • How does a headless CMS compare to using a framework such as Django CMS or Wagtail?
  • Can you describe what you have built at ButterCMS?
    • What was your motivation for starting a business to provide a CMS as a service?
  • How would you characterize the current state of the CMS ecosystem?
    • How does ButterCMS compare to the available open source and commercial options?
  • What are the trends in the web ecosystem that have made a headless CMS necessary or useful?
  • What types of information are people managing in a CMS?
  • How are people integrating headless CMS systems into their Python applications?
  • Can you describe the architecture for Butter?
    • How has the system changed or evolved since you first began working on it?
    • What was your decision process for determining what language(s) and technology stack to use for building the platform?
  • What are the aspects of building and maintaining a CMS that are most complex?
  • What are some of the most interesting, innovative, or unexpected ways that you have seen ButterCMS used?
  • What have you found to be the most interesting, unexpected, or challenging lessons that you have learned while building ButterCMS?
  • When is ButterCMS the wrong choice?
  • What do you have planned for the future of ButterCMS?

This article has been published from a wire agency feed without modifications to the text. Only the headline has been changed.

Source link

 

- Advertisment -Basics of Headless CMS 4Basics of Headless CMS 5

Most Popular

- Advertisment -Basics of Headless CMS 6Basics of Headless CMS 7