Listen "A Conversation about Migrating from a Legacy CMS to a Headless CMS"
Episode Synopsis
In this episode, I have a great conversation with full stack content architect Larry Swanson all about how to migrate from your legacy CMS into a headless CMS. We'll touch upon technology migration, content migration and the people and skills required for a successful migration and implementation.
===========================
Tell us about your background. How did you get into content?
You are a full stack content architect, can you explain what that means?
What are some examples of legacy CMSes?
What are some examples of Headless CMSes?
What does headless mean?
What does Single Source of Truth mean and why is that important when migrating to a headless CMS?
How is content managed in a headless CMS vs. a legacy one?
What mindset changes are recommended when migrating from legacy to headless?
What does API first mean?
What does microservices mean?
What are content types?
What is content modeling?
Talk about content design versus content intent and how that relates to a headless CMS?
Tell us about omni-channel strategy and multi-channel delivery and how is that implemented in a headless CMS?
What are some tips for authors migrating from a legacy CMS to a headless one?
What are some tips for developers?
What are some things you'll love in a headless CMS?
What are some things you'll miss from a legacy CMS?
What are some 'gottachas' you need to be aware of when migrating to a headless CMS?
Why should you migrate to a headless CMS?
What does the future hold in your opinion?
===========================
For more information on the Discover Headless Course,
please visit: https://www.headlesscreator.com/course/discover-headless-tech
===========================
Tell us about your background. How did you get into content?
You are a full stack content architect, can you explain what that means?
What are some examples of legacy CMSes?
What are some examples of Headless CMSes?
What does headless mean?
What does Single Source of Truth mean and why is that important when migrating to a headless CMS?
How is content managed in a headless CMS vs. a legacy one?
What mindset changes are recommended when migrating from legacy to headless?
What does API first mean?
What does microservices mean?
What are content types?
What is content modeling?
Talk about content design versus content intent and how that relates to a headless CMS?
Tell us about omni-channel strategy and multi-channel delivery and how is that implemented in a headless CMS?
What are some tips for authors migrating from a legacy CMS to a headless one?
What are some tips for developers?
What are some things you'll love in a headless CMS?
What are some things you'll miss from a legacy CMS?
What are some 'gottachas' you need to be aware of when migrating to a headless CMS?
Why should you migrate to a headless CMS?
What does the future hold in your opinion?
===========================
For more information on the Discover Headless Course,
please visit: https://www.headlesscreator.com/course/discover-headless-tech
ZARZA We are Zarza, the prestigious firm behind major projects in information technology.