Let's add the Device Content Type to the starter!

[jdcmsd]

Parent Issue

#24862

Problem Statement

The Device (previewDevice) feature, selectable in Edit/Preview/Live Mode, has been an undocumented feature for some time, and a frequent headache for Support. As of today, it's documented. However, it seems like a random bit of busywork to give to users — build this Content Type with these specific variables that dotCMS is already hard coded to look for.

Could we just include this as one of the Content Types that ships in our blank starters, etc., even if we don't instantiate any default Device contentlets?

Steps to Reproduce

This is more of a QoL deficiency than a per se bug: Spin up a blank dotCMS instance, and you'll need to create this Content Type with 8 fields by hand. I did it a few times while testing it; it's not a huge drag, but it does feel gratuitous.

Acceptance Criteria

New, blank dotCMS instances have the Device content type ready to go from the jump.

dotCMS Version

All versions that I can see, going back years.

Proposed Objective

User Experience

Proposed Priority

Priority 4 - Trivial

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

[github-actions]

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[nollymar]

A new empty starter has been generated to include the Device content type. Starter version: empty_20230710

[dcolina]

Internal QA PASSED.

Correctly added the Device (PreviewDevice) content type as part of the empty starter.

Step by step:

1. Load the web application and click on the content types menu.

2. Click on Device content type

[josemejias11]

Approved QA - Tested on master_183eee1_SNAPSHOT // Docker // macOS 13.0 // FF v113.0