Add experimental Trash module

Would it be possible to document why the decision was made to postpone this on the Workspaces? This module doesn't directly depend on Workspaces so it isn't self-explanatory why we would make it a hard blocker for this issue.

@lauriii we shouldn't add a new experimental module that is dealing with deep entity system architecture while we have one already in core that's not stable yet. And more specifically, the time spent working on trash module instead of resolving fundamental blockers to workspaces being is part of the reasons it didn't reach stable 2-3 years ago.

No longer postponed on Workspaces

Note there's now a stable trash module in contrib https://www.drupal.org/project/trash →

I haven't personally used it, but I believe it is the result of @amateescu's comment in #50.

Would the Trash → module be added to Drupal Core, or was it settled on only having it in Drupal CMS?

@rajab natshah that's what this issue is for deciding. For me personally I don't think there's an urgent need to have it in core because as far as I know it stable and working well in contrib. On the other hand 📌 Allow for / implement simplified content workflow with workspaces Active consolidates/reconciles two conflicting core modules and could potentially simplify aspects of trash module too, so that's the current priority in terms of the general area.

Yes, catch, with you.
The basic line: now, if we install Drupal Core, then add a node in any way, and delete it, it's gone forever (except if it was saved in the last backup).

We are happy with the current status, it is so nice in Drupal CMS now (Having this space for restoring deleted content) -
Thanks to the Drupal CMS team for pushing for stable data trash management.
Moving to adopt this logic in our products.
I landed on this issue as a part of my research and experimentation to follow up with this logic.

But it has issues with workflows, workspaces, and autosave.
As we worked on:

• 📌 [META] Track 13: Proposal for content publishing workflows Active
• 📌 Create Basic Content Publishing recipe Active

Noticed the move of logic to workspaces.

Having these extra fields in the database tables from the starting point of the site could ease many issues with contribs.
Also, the editorial UX/UI or API CRUD calls for JSON:API endpoints could be safer.