Back in the day, company had help center, documentation, API reference, e-learning, and certifications. Help center was in one tool, documentation and API reference in another tool and e-learning and certification in a third tool.
Customers told us when searching, they could not find. They reached out to support, which pointed them to a different system.
Headless CMS is best explained when compared to traditional CMS. Front end is decoupled from back end.
Can we even name all the solos? Split into categories: authoring silos and customer silos.
Authoring silos have complicated linking, separated teams, fragmented authoring, and multiplied maintenance. The more tools you have, the more things can break.
Customer silos have poor discoverability, fragmented user experience, fragmented search, and medium-oriented navigation.
The solution isn't just to throw everything into a headless CMS.
Idea to create one education portal.
Silos can be solved on the team level, but there might still be silos on the company level.
4 tips to become headless. Realize the impact. (Do the homework.) Plan well. (Don't underestimate thorough planning.) Ensure needed resources. (The bigger the project is, the more people you will need, and from different roles.) Iterate. (Implement one-by-one.)
No comments:
Post a Comment