Getting Started

ObjectCore is a practitioner-level knowledge base for the three major .NET DXP platforms: Sitecore, Umbraco, and Optimizely. Every article is built from research — version-specific, real-world tested, with honest tradeoffs. No vendor marketing, no surface-level overviews.

What you’ll find here

Platform deep-dives. Architecture decisions, implementation patterns, known issues, and migration paths — the kind of detail that experienced developers share with their teams but rarely publish.

Cross-platform comparisons. Genuine tradeoff analysis for teams evaluating platforms. Not feature checklists — decision frameworks based on your team size, budget, and technical requirements.

Migration guides. Step-by-step walkthroughs for common migration paths, with effort estimates, breaking changes, and rollback strategies.

Choose your platform

Each platform section covers architecture, implementation patterns, version-specific guidance, and known issues.

• Sitecore — XM Cloud architecture, composable DXP strategy, JSS/Next.js development, and migration paths from XP/XM on-prem.
• Umbraco — v14+ Bellissima backoffice, Content Delivery API, upgrade paths, content modeling, and the package ecosystem.
• Optimizely — CMS 12 on .NET 6+, Content Cloud, commerce catalog architecture, and experimentation tooling.

Start from your role

Developers and technical leads — Start with your platform’s overview page. Each one covers the current architecture, key APIs, and links to implementation guides.

Solution architects — The platform comparisons provide decision frameworks for platform selection. Migration guides include architectural analysis of source and target platforms.

Project managers — Platform overviews include ecosystem context — licensing models, hosting options, and partner landscapes — that inform project planning and vendor conversations.

Content authors and strategists — Platform overviews cover the content editing experience, content modeling approach, and multi-language capabilities for each platform.

How the content is built

Every article follows the same process:

1. Research — Platform behavior is verified against current versions through documentation review, community sources, and hands-on testing.
2. Structure — Content is organized by problem type, tagged by platform version, audience, and complexity level.
3. Review — Technical claims are cross-referenced. Confidence levels are stated. Gaps are flagged, not papered over.

When something is unverified or based on community reports rather than direct testing, the content says so.