Related practical notes
Connect different skills so content, visual design and implementation work towards the same project goal.
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.
Validate content, marketing and integrations together. Identify the product, version and editorial tasks before a migration prototype.
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
Where is my data anyway? Data sovereignty challenges in a world of SaaS and Cloud
Inventory storage, backups, logs and support access across services and regions. Check contracts and settings rather than primary hosting location alone.
Validate structured reuse, visual previews, approval and cache updates across the content and frontend boundary.
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.
Assess content, experimentation and marketing separately, including defaults, audience rules and traceable results.
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.
Identify the product and deployment model, then test editing, previews, permissions and external data.
Serve prebuilt pages statically and implement dynamic requests separately, with clear release, caching and private-data boundaries.
Next: Product information
Define product information responsibilities, inputs, collaborators and review outcomes. This page describes a discipline; staffing is agreed for each project.
