Get DXPR Builder onto a Drupal site, with or without DXPR CMS, and keep it current. The table points you to the page for your situation.
| I want to ... | Use | Needs |
|---|---|---|
| check my server and browsers first | System requirements | Nothing |
| start a new site with everything set up | Start a new site with DXPR CMS | A host for a new Drupal 11 site |
| add the builder to my existing site | Install DXPR Builder | Drupal 10.2 or later, Composer and a product key |
| use the builder on content types I already have | Use DXPR Builder on your content types | DXPR Builder installed |
| look at ready-made demo pages | Try DXPR Builder with demo pages | A browser, or a DXPR CMS test site |
| update to a newer release | Update DXPR Builder | A database backup |
| see what changed in a release | Changelog | Nothing |
| check my site after the Font Awesome 7 update | Font Awesome 7 in DXPR Builder | Access to your theme's CSS |
Which should I use
DXPR CMS wins when you start a new site: content types, demo pages and AI modules arrive set up. It does not fit a site you already run. There, install the DXPR Builder module, then switch your content types to the builder one by one.
Moving within the 3.x series is an update. Coming from 1.x or 2.x is a migration with extra checks.
Before you start
Every route that installs or updates the module needs Composer and Drush in your project, and an account that can install modules. The hosted demo needs only a browser.
What's next?
Install DXPR Builder to continue exploring DXPR Builder.