Technology selection
Technology selection
Compare editorial needs, functions, integrations, budget and team conditions. Prototype identical tasks and separate implementation from ongoing costs.
Working material
A content model defines independently maintained and reusable information. Authoring, preview, approval and publication form a workflow; an API response validates only one part.
Delivery and checks
Have real editors create, change and restore content using long headings, missing fields and multiple languages. Record development dependencies and release ownership.
Practical notes
Building a martech stack
Map acquisition, content, email, analytics and customer records, including existing tools. Before adding a system, check export, synchronisation and maintenance ownership.
Practical notes
How to choose the right CMS
Use an article, product and approval as sample tasks. Have real editors author, preview and restore content and record assistance and maintenance costs.
Practical notes
Choosing a DXP: Kentico Xperience or Optimizely
Prototype the same content model, approval task and integration list on each platform. Separate licensing, implementation and operational costs rather than comparing feature-list length.
Practical notes
Headless v Traditional CMS - which one is right for you?
Compare the same multi-page editing task, including preview, reuse and publishing. Include additional frontend maintenance in the decision.
Planning headless CMS content
Download this editable planning headless cms content to record current work, open questions and owners. OXOAK examples can be adapted to the project.
Practical notes
Choosing between Kentico Xperience and Kontent.ai
Compare authoring, preview, approval and release with the same update. Include frontend implementation and integration ownership in the evaluation.
Practical notes
Optimizely as a headless CMS
Verify retrieval, preview, routing and release triggers with appropriate API boundaries. The frontend still needs independent design and validation.
Practical notes
Choosing a DXP: Kentico Xperience or Umbraco CMS
Have real editors create, preview and restore a page. Record where development assistance is needed and include everyday editorial work in the platform decision.
Practical notes
Choosing a DXP: Kentico Xperience or Sitecore
Compare editing, approval, multisite and integration using the same tasks. Platform names cannot replace project-fit validation.
Practical notes
What is a composable DXP?
Map data flows between content, search, analytics and identity with failure owners. Replaceability requires real export and recovery paths.
Practical notes
There's still a place for the all-in-one DXP
Compare system count, editorial workflows and integration ownership. Independent replacement brings flexibility but also requires clear boundaries for failures, identities and suppliers.
Practical notes
Umbraco introduces composable DXP offering
Define interfaces for content, search, analytics and identity and preserve export and replacement paths. Test failure isolation before adding more systems.
