The content type recipes are not really part of Drupal CMS 2. They're in our dev dependencies, and have not been proper dependencies for the entire Drupal CMS 2.x development cycle.

They will continue to exist as handy standalone recipes for site templates to use, but site templates are allowed to have stronger opinions than our very generic content types can provide, really.

I propose the following:

  • In this issue, mark all of them as abandoned.
  • Tag 1.2.10 releases for all of them.
  • In this issue, remove them all from our subtree split.

Issue fork drupal_cms-3563583

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

phenaproxima created an issue. See original summary.

phenaproxima’s picture

Issue summary: View changes
Issue tags: +Drupal CMS stable release blocker

Tagging as a stable release blocker, since if we're going to do this, it's a significant release management change and needs to be done before we tag 2.0.0 stable.

phenaproxima’s picture

Issue summary: View changes
phenaproxima’s picture

Issue summary: View changes
pameeela’s picture

Yes, let's move page into content_type_base, and ditch the rest. The utility of these as generic recipes is a lot lower without including Canvas config, which then ties them to a specific theme. So it's not worth the overhead.

phenaproxima’s picture

Title: Remove the content type recipes from our subtree split, and make drupal_cms_page obsolete » Mark all the content type recipes as abandoned
Issue summary: View changes

  • phenaproxima committed 72b7bd50 on 1.2.x
    chore: #3563583 Mark all the content type recipes as abandoned
    
    By:...
phenaproxima’s picture

Status: Active » Fixed

Merged into 1.2.x and forward-ported to 2.x and 2.0.x.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

phenaproxima’s picture

Assigned: Unassigned » phenaproxima
Status: Fixed » Needs work

Actually, leaving open for the subtree split removal in the 2.x branches.

  • phenaproxima committed 93b0be0c on 2.x
    chore: #3563583 Mark all the content type recipes as abandoned
    
    By:...

  • phenaproxima committed 38a7e7b5 on 2.0.x
    chore: #3563583 Mark all the content type recipes as abandoned
    
    By:...

phenaproxima’s picture

Title: Mark all the content type recipes as abandoned » Remove all content type recipes from our subtree split

  • phenaproxima committed 11b97f8e on 1.2.x
    chore: #3563583 Remove all content type recipes from our subtree split...

phenaproxima changed the visibility of the branch 3563583-remove-from-subtree to hidden.

phenaproxima changed the visibility of the branch remove-ct-recipes to hidden.

phenaproxima’s picture

Issue summary: View changes

phenaproxima changed the visibility of the branch 3563583-sunset-everything to hidden.

  • phenaproxima committed cb13c488 on 2.x
    feat: #3563583 Remove all content type recipes from our subtree split...

  • phenaproxima committed c0817d4b on 2.0.x
    feat: #3563583 Remove all content type recipes from our subtree split...
phenaproxima’s picture

Assigned: phenaproxima » Unassigned
Status: Needs work » Fixed

It Is Done. This is a major, seismic refactoring that cements our move away from the more siloed/track-based approach of 1.x, towards holistic experiences in the form of site templates. Let's gooooo!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.