[ Feat : Expand Tutorial Deletion Option throughout the App ]

[rohitPandey469]

Is your feature request related to a problem? Please describe.
The current system lacks the capability to delete tutorials for both creators and users. Additionally, options such as reporting and downloading are missing for users. This limitation restricts content management and user interaction within the platform.

Describe the solution you'd like
I would like to add a delete tutorials options for creators ( with a conformation screen ), heavily focused on feeds section and possibly an option to delete wherever the creator can navigate to edit the tutorials or view tutorials.

Describe alternatives you've considered
Could follow a model similar to GitHub, where the option to delete or move to trash is centralized in the settings. However, this might result in a less intuitive user experience. The preferred solution is to incorporate the delete option directly within the feed, offering more immediate and accessible control.

Additional context
Consider implementing the "Delete Tutorial" option in three key locations: a vertical outlined dropdown, when viewing all tutorials for a specific organization, and as a "Move to Trash" option. Alternatively, a centralized delete option in the organization settings (profile settings) akin to GitHub could also be considered. This flexibility ensures a user-friendly and versatile approach to content management

Codelabz.-.Google.Chrome.2024-01-11.09-34-47.mp4

[rohitPandey469]

@Sarfraz-droid @ABHISHEK-PANDEY2 @shivareddy6 What are your thoughts having delete options at multiple places giving more flexibility and ease content management or a decentralized delete system akin to Github.

[rohitPandey469]

#1032 have already fixed the issue and better than me however I would like to scale the delete option to vertical outlined dropdown and when viewing all tutorials for specific organization

[github-actions]

This issue is stale because it has been open for 30 days with no activity.

[github-actions]

This issue was closed because it has been inactive for 14 days since being marked as stale.