My Headless CMS Skills:
- Strapi CMS
- Contentful CMS
- TinaCMS Realtime Editing
Content powers our Digital World. It’s the new front-door to connect with customers on tons of different devices, device sizes, operating systems, etc. Creating and Managing digital experiences using a Traditional Monolithic CMS is really tough plus you get locked in. Example: You built a Web app with Monolithic Wordpress Technology, but you are now locked in as you are unable to create a Mobile App or a TV App or a Watch App or whatever new platform that just came, you are just unable to support them because the Monolithic Wordpress Backend is just not compatible with New Technology. That’s where Headless CMS comes in to the picture.
As digital platforms have evolved, the need for more flexible solutions has emerged. Now, enterprises are developing websites, mobile sites, apps, digital displays, conversational interfaces and more. Meanwhile, the traditional CMS has failed to keep pace. Why? Because a Traditional CMS organizes content in a traditonal webpage-oriented frameworks, making it impossible for the same content to adapt to other digital platforms.
A Headless CMS, is a back-end-only content management system that acts primarily as a content repository. A headless CMS makes content accessible via an API for display on any device, without a built-in front-end or presentation layer. The term “headless” comes from the concept of chopping the “head” (the front end) off the “body” (the back end). ~ Wikipedia
Simply put, a headless CMS is a content management system that manages and organizes content without a connected front-end or display layer. The headless CMS is where all of your content and assets live. Then, you use a Content API which the Developer can access via REST or GraphQL endpoints and build the frontend the way the Developer/Designer/Company would like it to be so that they can be distributed to anywhere and everywhere you need it — your website, your mobile app, your email marketing, your CRM, etc.
Harry is a motivated developer who focuses on completing any work that gets assigned to him, totally invested and dedicated to the project at hand. I had a great time coordinating with him due to his detailed reports and positive attitude. It never was a problem for him to communicate through Slack or via a call to define or solve any issues, even if that meant working outside his working hours due to the workload or timezone differences. Continuously finishing courses related to the field he's working on and other interesting/new technologies/frameworks, he was fast to share with the team any interesting tech-news that were related to our stack or project.