Table of Contents

New to DynamicWeb?

An overview of the main product areas, implementation options, and where to start learning

This article is an introduction to DynamicWeb 10. It is intended for readers who are new to the platform and need a high-level overview before diving into more specific documentation.

Use this page to understand:

  • What DynamicWeb includes
  • Which main areas you work in
  • How solutions are implemented
  • Where to continue, depending on your role

What DynamicWeb is

DynamicWeb combines several business and content capabilities in one platform.

At a high level, DynamicWeb includes:

  • CMS for content management and website structure
  • Products and PIM for product information, enrichment, and publication
  • Commerce for orders, pricing, and promotions
  • Integration for connecting DynamicWeb to external systems
  • Swift as a low-code implementation option for selected projects

DynamicWeb 10 is built on modern .NET technology and supports several implementation approaches, including server-rendered, low-code, and headless solutions.

To access the administration interface of a DynamicWeb solution, add /admin to the solution URL:

www.yoururl.com/admin

Then sign in with the backend credentials provided for the solution.

Main product areas

The main areas in DynamicWeb 10 are described below. Together, they cover the most common day-to-day work in the platform.

CMS

The CMS areas are where you create and manage websites and content - they include:

  • The Content area for page structure, page editing, and navigation ContentArea
  • The Assets area for managing files, images, and other digital assets AssetsArea
  • The Users area for backend users, frontend users, and related account management UsersArea

For many teams, this is the area where editors and administrators spend most of their time.

Products and PIM

The Products area is where you work with product data and enrichment.

This area supports Product Information Management (PIM) and related product workflows, including:

  • Product data models
  • Queries and workspaces
  • Enrichment processes
  • Channel-specific publication
  • Customer assortments

ProductArea

This is one of the most feature-rich areas in DynamicWeb and is often central to B2B, B2C, and omnichannel implementations.

Commerce and email

The Commerce area contains tools for commercial workflows such as:

CommerceArea

The Email area contains DynamicWeb's email marketing and segmentation tools.

MarketingArea

Integration

DynamicWeb includes a built-in integration framework for connecting to external systems such as ERP systems and other business platforms.

At a high level, DynamicWeb integrations are request-driven:

  1. DynamicWeb sends a request to an external service
  2. The external service returns a response
  3. DynamicWeb reads, maps, and persists the returned data where relevant

The Integration area is where you configure endpoints and integration activities.

If you work with integrations, it helps to understand both the external system and the data model inside DynamicWeb.

DynamicWeb Swift

DynamicWeb Swift is DynamicWeb's standard low-code implementation option for creating a storefront. It is designed to help teams create websites quickly using configurable building blocks and best-practice patterns.

Swift

Warning

Swift is not the same thing as DynamicWeb itself.

Swift is one implementation option built on top of DynamicWeb. It does not automatically expose every platform feature, and new platform features are not automatically available in Swift.

If needed, Swift can be customized and extended, but it should still be treated as a specific implementation layer rather than as the full platform.

How DynamicWeb solutions are implemented

There are three common ways to implement a DynamicWeb solution:

  • Use DynamicWeb Swift for a low-code starting point
  • Build a custom server-rendered solution with C# Razor
  • Build a headless solution using delivery APIs

Each approach has different tradeoffs in flexibility, speed, maintenance, and frontend ownership.

How DynamicWeb solutions are extended

DynamicWeb 10 includes a broad extensibility model for developers.

Common extension scenarios include:

  • Custom screens and UI elements
  • Notification subscribers and other extension points
  • Custom providers and configurable add-ins
  • ViewModel extensions and template-related customizations

If you want to build custom code, start with one of these setup guides:

Then continue with Extending DynamicWeb.

Where to go next

Choose the next article based on what you need to do:

Improve this doc
To top