Options for Reusing the Demo Site

The demo site is designed to be reused in different ways depending on what you need to change and how much separation you want from the shared environment.

For most solution consultants, the right choice comes down to one question: do you need a quick space for content changes, a fully independent copy, or an isolated demo environment without setting up your own repository? This guide outlines the three available options and when to use each one.

Use Drafts Area

The simplest way to reuse the demo site is to work in the `/drafts` area and create content inside your own dedicated user folder.

This approach is best when you want to:

• create or test new pages
• adapt messaging for a customer conversation
• preview and publish content safely
• experiment without affecting the main demo site structure

Using /drafts is the fastest option because it does not require a separate repository or site setup. It gives you a safe working area for authoring and iteration while keeping the shared demo environment stable for everyone else.

NOTE : As a team practice, avoid editing the main demo content area directly. Use the Drafts folder and your personal folder instead. This keeps experiments isolated, reduces accidental changes, and makes collaboration easier.

Use Github Template

If you need full ownership of the codebase and content setup, use the baseline Demo site repository and rely on 'Use Template' option to create your own detached copy of the demo site in your GitHub space.

This option is best when you want to:

• make larger structural or code changes
• manage your own repository independently
• build a longer-lived version of the demo
• experiment freely without any impact on the shared demo environmentd

This path gives you the most flexibility, but it also requires more setup. In addition to creating the repository, you may need to import pages with the DA Import tool and configure supporting pieces such as the block library, configs, and other site-level settings.

Choose this option when you want a fully independent environment and are comfortable owning both the content and the implementation.

Request for a clone

If you want a dedicated version of the demo site without creating and managing your own GitHub-based copy, request a clone through the Slack Channel #aem-da-scdemos

Admins can create a true clone of the demo site as a repoless site, giving you an isolated space for content changes, testing, and customer-specific adaptation.

This option is best when you want:

• a dedicated demo space
• stronger separation from the shared site
• a simpler setup than creating a new repository
• a safe environment for customer-facing demo preparation

A clone is especially useful when you need a focused environment for a particular account, industry narrative, or workshop flow, but do not want the overhead of setting up and maintaining your own full repo and content structure.