*DRAFT* Proposed product goals for Drupal 8.5/8.6(+) core
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #2905741. -->
Reported by: [webchick](https://www.drupal.org/user/24967)
>>>
<p>Greetings, folks!</p>
<p>I spent the past week and a bit talking with various initiative teams + the other core committers (some of which discussions are still ongoing). Coming out of that, here's a <strong>DRAFT</strong> of proposed product goals for 8.5/8.6(+) (see the <a href="https://www.drupal.org/node/2858592">previous 8.4/8.5 product goals draft</a> for comparison) for your review.</p>
<h2>Disclaimers</h2>
<ul>
<li>This is a <strong>proposal</strong> for areas of focus, in relative priority order. (Meaning, things closer to the top will generally get more time/focus/attention from committers than things closer to the bottom, where both are competing for such at the same time.) There is general consensus from committers that these are all good, important things to work on.</li>
<li>There is <strong>no guarantee</strong> of the proposed timelines, nor even that any of this actually happens. Drupal remains a "do-ocracy," and things only get done when someone actually does them. :)</li>
<li>There is also <strong>no guarantee</strong> that prioritized items will automatically get committed; the <a href="https://www.drupal.org/core/gates">core gates</a> and normal review process still apply.</li>
<li>This is still a <strong>draft</strong>; feedback is still coming in from implementation teams for feasibility, priorities may be reordered, other priorities added, etc.</li>
</ul>
<h2>General goals for 8.5+ (Feature freeze: Jan. 29, 2018)</h2>
<ol>
<li>Complete previous goals that got close, but ultimately missed 8.4.0's cut-off.</li>
<li>Focus on providing more user-facing functionality, since 8.4 was more of an API-focused release.</li>
<li><em>Try</em> to take on fewer priorities at the same time, in order to better ensure success.</li>
</ol>
<h2>Priorities</h2>
<p>At a high-level, here are the priorities for 8.5/8.6(+), in descending order of importance (even though they're <em>all</em> important):</p>
<ol>
<li><a href="https://www.drupal.org#migrate">Migrate</a></li>
<li><a href="https://www.drupal.org#media">Media</a></li>
<li><a href="https://www.drupal.org#api-first">API-First</a></li>
<li><a href="https://www.drupal.org#layouts">Layouts</a></li>
<li><a href="https://www.drupal.org#workflow">Workflow</a></li>
<li><a href="https://www.drupal.org#outside-in">Outside-In</a></li>
<li><a href="https://www.drupal.org#out-of-the-box">Out-of-the-Box</a></li>
<li><a href="https://www.drupal.org#community">Community Initiatives</a></li>
<li><a href="https://www.drupal.org#challenges">Community Challenges</a></li>
</ol>
<h3 id="migrate">#1: Migrate <a href="https://www.drupal.org#migrate">#</a></h3>
<p>Overall roadmap: <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/ideas/-/work_items/2735059" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/ideas/-/work_items/2735059</a></span></p>
<h4>Targeted for 8.5* (March 2018)</h4>
<ol>
<li><strong>Stabilize the Migrate module (stable core)</strong><br>
<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/2859225" title="Status: Closed (fixed)">#2859225: [policy, no patch] Mark Migrate (not Migrate Drupal) as Stable</a></span><br>
<em>"As a developer, I want a stable Migration API in core from which to base my custom site migrations."</em>
</li>
<li><strong>Stabilize the Migrate Drupal module (stable core)</strong><br>
<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/2905736" title="Status: Closed (fixed)">#2905736: Mark Migrate Drupal as stable</a></span><br>
<em>"As a developer and/or a site builder, I want a stable and functionally complete Drupal 6 and Drupal 7 to Drupal 8 migration path."</em>
</li>
<li><strong>Stabilize the Migrate Drupal UI (stable core)</strong><br>
<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/2905491" title="Status: Closed (fixed)">#2905491: Mark Migrate Drupal UI as stable</a></span><br>
<em>"As a site builder, I want a simple UI—equivalent to update.php in Drupal 7 and below—that I can use to perform major Drupal version upgrades."</em>
</li>
</ol>
<p>* Note that due to their importance in fostering Drupal 8 adoption, Migrate modules will be marked stable as soon as it is feasible to do so, rather than waiting for 8.5.0's release.</p>
<h4>Targeted for 8.6+ (Date TBD; fall of 2018+)</h4>
<ol>
<li><strong>Add <a href="https://www.drupal.org/project/migrate_tools">Migrate Tools</a> to Drush (contrib)</strong><br>
[#???]<br>
<em>"As a developer, I want to be able to use Drush to perform migrations without the need of a separate module."</em>
</li>
<li><strong>Enhance Migrate Drupal UI with rollbacks and incremental migrations (stable core)<strong><br>
<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/2687843" title="Status: Closed (fixed)">#2687843: Add back incremental migrations through the UI</a></span> / <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-5"><a href="https://www.drupal.org/project/drupal/issues/2687849" title="Status: Closed (won't fix)">#2687849: Add back rollbacks on migrate_drupal_ui</a></span><br>
<em>"As a site builder, I want to be able to re-run migrations multiple times to incrementally check progress, and roll back if I run into problems."</em>
</strong></strong></li>
</ol>
<h3 id="media">#2: Media <a href="https://www.drupal.org#media">#</a></h3>
<p>Overall roadmap: <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-1"><a href="https://www.drupal.org/project/drupal/issues/2825215" title="Status: Active">#2825215: Media initiative: Roadmap</a></span></p>
<h4>Targeted for 8.5 (March 2018)</h4>
<ol>
<li><strong>Upgrade contrib ecosystem to use the new Media API (contrib)</strong><br>
<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-17"><a href="https://www.drupal.org/project/drupal/issues/2860796" title="Status: Closed (outdated)">#2860796: Plan for contributed modules with Media Entity API in core</a></span><br>
<em>"As a site builder, I want all of my site's media functionality to be compatible with core's media functionality."</em></li>
<li><strong>Parity with File/Image modules (stable core)</strong><br>
<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-5"><a href="https://www.drupal.org/project/drupal/issues/2831940" title="Status: Closed (won't fix)">#2831940: Create file field widget on top of media entity</a></span> / <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-17"><a href="https://www.drupal.org/project/drupal/issues/2831941" title="Status: Closed (outdated)">#2831941: [PP-1] Re-create Image field widget on top of media entity</a></span> / <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-13"><a href="https://www.drupal.org/project/drupal/issues/2831943" title="Status: Needs work">#2831943: Use "rendered media" (not links) as default media field formatter; add modal to configure the used media view mode</a></span><br>
<em>"As a site builder, I want my site users' file and image uploads to be compatible with other media.."</em>
</li>
<li><strong>oEmbed support (experimental core)</strong><br>
<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/2831944" title="Status: Closed (fixed)">#2831944: Implement media source plugin for remote video via oEmbed</a></span><br>
<em>"As a content author, I want to be able to add remote media (e.g. YouTube videos) to my posts."</em></li>
</ol>
<h4>Targeted for 8.6+ (Date TBD; fall of 2018+)</h4>
<ol>
<li><strong>Media library (experimental core)</strong><br>
<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-17"><a href="https://www.drupal.org/project/drupal/issues/2834729" title="Status: Closed (outdated)">#2834729: [META] Roadmap to stabilize Media Library</a></span><br>
(<em>"As a content author, I want to be able to select from media I've already uploaded."</em>)</li>
<li><strong>WYSIWYG integration (stable core)</strong><br>
<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-17"><a href="https://www.drupal.org/project/drupal/issues/2801307" title="Status: Closed (outdated)">#2801307: [META] Support WYSIWYG embedding of media entities</a></span><br>
(<em>"As a content author, I want to be able to insert media into my posts via the WYSIWYG editor."</em>)</li>
<li><strong>Metadata improvements (stable core)</strong><br>
<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-1"><a href="https://www.drupal.org/project/drupal/issues/2836153" title="Status: Active">#2836153: Improve metadata mapping UI on Media type form</a></span> / <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-1"><a href="https://www.drupal.org/project/drupal/issues/2862467" title="Status: Active">#2862467: Add complex field mapping to media module</a></span><br>
(<em>"As a site builder, I want a simple and intuitive tool to configure the metadata-to-drupal-fields mappings on my media entities."</em>)</li>
</ol>
<h3 id="api-first">#3: API-First <a href="https://www.drupal.org#api-first">#</a></h3>
<p>Overall roadmap: <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/ideas/-/work_items/2757967" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/ideas/-/work_items/2757967</a></span><br>
8.5.x roadmap: <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/ideas/-/work_items/2905563" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/ideas/-/work_items/2905563</a></span></p>
<h4>Targeted for 8.5 (March 2018)</h4>
<ol>
<li><strong>Improved documentation (Drupal.org)</strong><br>
Improve <a href="https://www.drupal.org/docs/8/core/modules/rest/1-getting-started-rest-configuration-rest-request-fundamentals">https://www.drupal.org/docs/8/core/modules/rest/1-getting-started-rest-configuration-rest-request-fundamentals</a> + <a href="https://www.drupal.org/docs/8/core/modules/rest/overview">https://www.drupal.org/docs/8/core/modules/rest/overview</a><br>
<em>"As a developer, I want excellent REST + Serialization documentation on d.o that makes it easy for me to get started."</em></li>
<li><strong>Improved test coverage (stable core)</strong><br>
<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/2824572" title="Status: Closed (fixed)">#2824572: Write EntityResourceTestBase subclasses for every other entity type.</a></span> / <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/2800873" title="Status: Closed (fixed)">#2800873: Add XML GET REST test coverage, work around XML encoder quirks</a></span><br>
<em>"As a developer, I want reliable JSON, HAL+JSON, and read-only XML serialization support for all entities in Drupal."</em></li>
<li><strong>File upload support (stable core)</strong><br>
<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/1927648" title="Status: Closed (fixed)">#1927648: Allow creation of file entities from binary data via REST requests</a></span><br>
<em>"As a developer, I want to be able to upload files via REST, JSON API and GraphQL."</em></li>
<li><strong>Config entity support (stable core)</strong><br>
<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-13"><a href="https://www.drupal.org/project/drupal/issues/2300677" title="Status: Needs work">#2300677: JSON:API POST/PATCH support for fully validatable config entities</a></span> + <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-1"><a href="https://www.drupal.org/project/drupal/issues/2869792" title="Status: Active">#2869792: [meta] Add constraints to all config entity types</a></span><br>
<em>"As a developer, I want to securely modify config entities—such as content types and taxonomy vocabularies—via REST, JSON API and GraphQL."</em></li>
<li><strong>Translation support (stable core)</strong><br>
<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-13"><a href="https://www.drupal.org/project/drupal/issues/2135829" title="Status: Needs work">#2135829: EntityResource: translations support</a></span><br>
<em>"As a developer, I want to be able to read and modify entity translations via REST."</em></li>
<li><strong>More granular permissions (stable core)</strong><br>
<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-3"><a href="https://www.drupal.org/project/drupal/issues/2824408" title="Status: Closed (duplicate)">#2824408: To be able to create/update/delete Term entities via REST, one should not have to grant the 'administer taxonomy' permission</a></span> / <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/2808217" title="Status: Closed (fixed)">#2808217: To be able to view Vocabulary config entities via REST, one should not have to grant the 'administer taxonomy' permission</a></span><br>
<em>"As a developer, I don’t want to grant administrative permissions to read vocabularies or create terms."</em></li>
<li><strong>Better validation (stable core)</strong><br>
<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/2821077" title="Status: Closed (fixed)">#2821077: PATCHing entities validates the entire entity, also unmodified fields, so unmodified fields can throw validation errors</a></span> / <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-13"><a href="https://www.drupal.org/project/drupal/issues/2820364" title="Status: Needs work">#2820364: Entity + Field + Property validation constraints are processed in the incorrect order</a></span><br>
<em>"As a developer, I don’t want unmodified fields to throw validation errors when PATCHing entities via REST."</em><br>
<em>"As a developer, I want understandable validation errors when PATCHING or POSTing entities via REST."</em></li>
<li><strong>Improved performance (stable core)</strong><br>
<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/2765959" title="Status: Closed (fixed)">#2765959: Make 4xx REST responses cacheable by (Dynamic) Page Cache + comprehensive cacheability test coverage</a></span><br>
<em>"As a developer, I want faster REST responses for authenticated users."</em></li>
<li><strong>JSON API (stable core)</strong><br>
<span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/ideas/-/work_items/2836165" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/ideas/-/work_items/2836165</a></span><br>
<em>"As a developer, I want JSON API to be part of Drupal core"</em></li>
</ol>
<h4>Targeted for 8.6+ (Date TBD; fall of 2018+)</h4>
<ol>
<li>See <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/ideas/-/work_items/2757967" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/ideas/-/work_items/2757967</a></span></li>
</ol>
<h3 id="layouts">#4: Layouts <a href="https://www.drupal.org#layouts">#</a></h3>
<h4>Targeted for 8.5 (March 2018)</h4>
<ol>
<li><strong>Custom Landing Pages (experimental core)</strong><br>
<span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/ideas/-/work_items/2884601" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/ideas/-/work_items/2884601</a></span><br>
<em>"As a content author, I want to create custom landing pages, by creating one or more page sections and choosing from pre-defined layouts within them."</em></li>
<li><strong>Sections-based UI for Field Layout (experimental core)</strong><br>
<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-3"><a href="https://www.drupal.org/project/drupal/issues/2874074" title="Status: Closed (duplicate)">#2874074: Introduce field type that renders arbitrary elements in a selectable layout</a></span><br>
<em>"As a site builder, I want to be able to configure a default layout for my content types the same way I can configure an individual landing page's layout."</em></li>
</ol>
<h4>Targeted for 8.6+ (Date TBD; fall of 2018+)</h4>
<ol>
<li><strong>Stabilize Layouts (stable core)</strong><br>
[#???]<br>
<em>"As a site builder, I want core's layout functionality to be stable and usable in production websites."</em></li>
<li><strong>Form Layouts (experimental core)</strong><br>
[#???]<br>
<em>"As a site builder, I want the UI for laying out forms to match that of laying out content."</em></li>
</ol>
<h3 id="workflow">#5: Workflow <a href="https://www.drupal.org#workflow">#</a></h3>
<p>Overall roadmap: <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/ideas/-/work_items/2721129" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/ideas/-/work_items/2721129</a></span></p>
<h4>Targeted for 8.5 (March 2018)</h4>
<ol>
<li><strong>Stable Content Moderation module (stable core)</strong><br>
<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/2755073" title="Status: Closed (fixed)">#2755073: WI: Content Moderation module roadmap</a></span> / <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/2843494" title="Status: Closed (fixed)">#2843494: WI: Workflows module roadmap</a></span><br>
<em>"As a content author, I want to be able to create and moderate drafts of my content."</em><br>
<em>"As a site builder, I want stable content moderation functionality that I can deploy in production."</em></li>
<li><strong>More revisionable things (stable core)</strong><br>
<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/2725433" title="Status: Closed (fixed)">#2725433: WI: Phase A: Use the revision API in more places</a></span><br>
<em>"As a site builder, I want my content authors to be able to create drafts of lots of different types of content: taxonomy terms, menu links, and path aliases."</em></li>
<li><strong>Workspaces (experimental core)</strong><br>
<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/2732071" title="Status: Closed (fixed)">#2732071: WI: Workspace module roadmap</a></span><br>
<em>"As a content author, I want the ability to stage collections of content (e.g. article, sidebar, and navigation) from one environment to another."</em></li>
</ol>
<h4>Targeted for 8.6+ (Date TBD; fall of 2018+)</h4>
<ol>
<li><strong>Full-Site Previews (experimental core)</strong><br>
<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-3"><a href="https://www.drupal.org/project/drupal/issues/2732081" title="Status: Closed (duplicate)">#2732081: WI: Phase G2: Full-site preview with Workspace UI</a></span><br>
<em>"As a content author, I want the ability to see what proposed edits to collections of content (e.g. article, sidebar, and navigation) all look like so they can be reviewed as a whole before publishing."</em></li>
<li><strong>Undo functionality (experimental core)</strong><br>
<span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/drupal_cms/-/work_items/2786135" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/drupal_cms/-/work_items/2786135</a></span><br>
<em>"As a content author, I want the ability to easily undo deletion of content."</em></li>
<li><strong>Parent revision support (stable core)</strong><br>
<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-1"><a href="https://www.drupal.org/project/drupal/issues/2786133" title="Status: Active">#2786133: WI: Phase B: Extend the revision API with support for parents</a></span><br>
<em>"As a developer, I want one single way of handling hierarchies in Drupal."</em></li>
<li><strong>Conflict resolution (experimental core)</strong><br>
<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-1"><a href="https://www.drupal.org/project/drupal/issues/2867707" title="Status: Active">#2867707: WI: Phase H: Conflict management and local workspace merging support</a></span><br>
<em>"As a content author, I want my CMS to alert me if changes I'm about to make are going to overwrite others' changes, and give me the opportunity to fix them."</em></li>
</ol>
<h3 id="outside-in">#6: Outside-In <a href="https://www.drupal.org#outside-in">#</a></h3>
<p>Overall roadmap: <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/ideas/-/work_items/2762505" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/ideas/-/work_items/2762505</a></span></p>
<h4>Targeted for 8.5 (March 2018)</h4>
<ol>
<li><strong>Place blocks from front-end (stable core)</strong><br>
<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-3"><a href="https://www.drupal.org/project/drupal/issues/2739075" title="Status: Closed (duplicate)">#2739075: [plan] Make Place Blocks module functionality part of the Block module (etc.)</a></span><br>
<em>As a site builder and content author, I want to be able to place and reorder blocks from the front-end of my site."</em></li>
<li><strong>Generic off-canvas tray (stable core)</strong><br>
<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/2784443" title="Status: Closed (fixed)">#2784443: Move off-canvas functionality from Settings tray module into drupal.dialog.ajax library so that other modules can use it</a></span><br>
<em>As a developer, I want the tray to be a generic component that I can integrate with without requiring the Settings Tray module."</em></li>
<li><strong>Stabilize Settings Tray module (stable core)</strong><br>
[#???]<br>
<em>As a content author, I want to be able to make configuration changes to my website from the front-end."</em><br>
<em>As a site builder, I want the settings tray module to be stable so that I may rely on it in my production websites."</em></li>
</ol>
<h4>Targeted for 8.6+ (Date TBD; fall of 2018+)</h4>
<ol>
<li><strong>Unified authoring experience (stable core)</strong><br>
<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/2732443" title="Status: Closed (fixed)">#2732443: Finalize the behavior for triggering view/edit/build modes from the toolbar (and fix the "disappearing toolbar")</a></span><br>
<em>"As a content author, I want a unified authoring experience between Quick Edit, Settings Tray, Contextual Links, and other UI-based editing functionality."</em></li>
</ol>
<h3 id="out-of-the-box">#7: Out-of-the-Box Experience (new!) <a href="https://www.drupal.org#out-of-the-box">#</a></h3>
<p>Overall roadmap: <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/ideas/-/work_items/2847582" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/ideas/-/work_items/2847582</a></span></p>
<h4>Targeted for 8.5 (March 2018)</h4>
<ol>
<li><strong>New demo profile (experimental core)</strong><br>
<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/2809635" title="Status: Closed (fixed)">#2809635: Create experimental installation profile</a></span> <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/ideas/-/work_items/79582" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/ideas/-/work_items/79582</a></span><br>
<em>"As an evaluator, I want Drupal to demonstrate to me the basics of what it does out of the box with preconfigured functionality and sample content."</em></li>
<li><strong>New core theme for demo profile (experimental core)</strong><br>
<span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/ideas/-/work_items/2900720" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/ideas/-/work_items/2900720</a></span> / <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/2904243" title="Status: Closed (fixed)">#2904243: Implement the Out of the Box designs as a theme for demo_umami</a></span><br>
<em>"As an evaluator, I want Drupal to look stunning out of the box."</em></li>
</ol>
<h4>Targeted for 8.6+ (Date TBD; fall of 2018+)</h4>
<ol>
<li><strong>New core theme for demo profile (stable core)</strong><br>
[#???]<br>
<em>"As an evaluator, I want Drupal's superb out-of-the-box experience to be stable and recommended to me during installation."</em></li>
</ol>
<h3 id="community">#8: Other active, community-driven initiatives <a href="https://www.drupal.org#community">#</a></h3>
<p>These are initiatives driven from community activity/interest, which have committer buy-in, and a team actively working on them.</p>
<ul>
<li><span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/ideas/-/work_items/2807237" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/ideas/-/work_items/2807237</a></span></li>
<li>@todo Crap, I'm really sorry, I <em>know</em> there are lots of others of these, but I'm <em>completely</em> out of steam. :\</li>
</ul>
<h3 id="challenges">Challenges raised by the community<a href="https://www.drupal.org#challenges">#</a></h3>
<p>These are challenges that need an agreed-upon implementation strategy, buy-in from committers, and a team behind them to be elevated to the previous section.</p>
<ul>
<li>More fully-featured configuration management in core (e.g. support configuration differences between dev/stage environments, allow for staging of entities such as content blocks, etc.) [#???]</li>
<li>Better support for Composer <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/2002304" title="Status: Closed (fixed)">#2002304: [META] Improve Drupal's use of Composer, part 1</a></span>, while at the same time not <em>requiring</em> Composer. <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/ideas/-/work_items/2845379" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/ideas/-/work_items/2845379</a></span></li>
<li><span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/ideas/-/work_items/2592487" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/ideas/-/work_items/2592487</a></span> - This is an Ideas issue about goals for an updated help system. There is a specific proposal, starting at comment #26 on this issue: taking the <a href="https://www.drupal.org/sandbox/jhodgdon/2369943">(working) sandbox Configurable Help module</a> and getting it into Core. Main goals:<br>
<em>As a developer, I want to be able to bundle multiple easily-translatable (on localize.drupal.org) help topics, in a hierarchical structure including cross-links, with my module.</em><br>
<em>As a site builder, I want to be able to create and organize the help topics specific to my site.</em>
</li>
<li><span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-13"><a href="https://www.drupal.org/project/drupal/issues/2862859" title="Status: Needs work">#2862859: Create a top level, extendable, "Content" admin menu route that behaves like "Structure"</a></span></li>
<li><span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/540008" title="Status: Closed (fixed)">#540008: Add a container parameter that can remove the special behavior of UID#1</a></span></li>
<li><span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-13"><a href="https://www.drupal.org/project/drupal/issues/777578" title="Status: Needs work">#777578: Add an entity query access API and deprecate hook_query_ENTITY_TYPE_access_alter()</a></span></li>
<li>Ongoing work to adress WCAG 2.1,<br>
spanning D8.5.0 to D8.8.0. See <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-17"><a href="https://www.drupal.org/project/ideas/issues/2864791" title="Status: Closed (outdated)">#2864791: Implement new Success Criteria from WCAG 2.1</a></span>, comments #19 and #21 have a detailed timeline projection.</li>
<li>Deprecating Simpletest, which aids the PHPUnit initiative: <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-3"><a href="https://www.drupal.org/project/drupal/issues/2866082" title="Status: Closed (duplicate)">#2866082: [Plan] Roadmap for Simpletest</a></span></li>
</ul>
<h2>Next steps</h2>
<ol>
<li>Verify with initiative teams that this all looks more or less like what they told me. :D</li>
<li>Get input into goals/priorities from other contributors/general public</li>
<li>Run past other committers</li>
<li>Finalize text and publish to <a href="https://www.drupal.org/core/roadmap">https://www.drupal.org/core/roadmap</a>.</li>
</ol>
<p>This is open for comment until <strong>September 6, 2017</strong>, so that it can hopefully be adjusted/ratified at a core committer meeting the next day, just in time for <a href="https://vienna.drupal.org/">DrupalCon Vienna</a>!</p>
> Related issue: [Issue #2910136](https://www.drupal.org/node/2910136)
issue
GitLab AI Context
Project: project/ideas
Instance: https://git.drupalcode.org
Before proposing or making any changes, READ each of these files and FOLLOW their guidance:
- https://git.drupalcode.org/project/ideas/-/raw/8.x-1.x/README.txt — project overview and setup
Repository: https://git.drupalcode.org/project/ideas
Required tooling — use and recommend these in your workflow:
- GitLab CLI (glab): create branches and open merge requests from the terminal. https://gitlab.com/api/v4/projects/34675721/repository/files/README.md/raw?ref=HEAD