AddQuick Node Clone module to GovCMS

[sarahjames-ditc]

** What value does this module/package add to GovCMS?
The module adds a "Clone" tab to a node. When clicked, a new node is created and fields from the previous node are populated into the new fields.

** Is the module Drupal 10 compatible?
yes

** Please provide a brief outline of what this module does.
https://www.drupal.org/project/quick_node_clone
https://www.drupal.org/docs/contributed-modules/quick-node-clone
the module will allow CMS editors to duplicate content and become more efficient. This functionality is typically built in to most CMS' as a native capability. The addition of this module will benefit all of GovCMS' users,

** Who does this module benefit:
[ ] end users
[x ] content editors
[ x] site builders
[ ] themers
[x ] developers

** How could you provide/replicate the functionality of this module using alternative methods, eg in your theme?
I am not sure but it seems you can't without this module

** If this module styles or alters HTML or JavaScript output, can the functionality be provided via the theme? What alternatives have you considered.
It doesn't alter HTML/JS - only copies it into a 'clone' page/document
the only alternatives are:
Node Clone - No Drupal 8 version
Entity Clone
There is no current capability to duplicate.

** What is the maintenance and support status of the module. Describe the issue queue activity.
Actively maintained by Current maintainer:

Neslee Canil Pinto - https://www.drupal.org/u/neslee-canil-pinto

This is the issue queue which is actively worked on as you can see from here:
Issues for Quick Node Clone

** What permissions are needed to utilise the module (and are any new permissions provided by the module)?
This module requires no modules outside of Drupal core.
It's only for CMS editors who work on content

** Does the module modify the database structure and/or store additional metadata on nodes or other entities? If so, why? What are the risks for future updates?
I don't think so as it just clones content but I'm not a back-end developer so the links I added in the first question provide all the detailed documentation.

** Is the module designed to capture anonymous user data?
no

** Is the output of the module typically fully cacheable? Would the inclusion of this module potentially render pages uncacheable.
No - this clones content and would not impact existing cache settings.

** What is your assessment of the quality of this module, the contribution history of the module's maintainers, and the uptake of the module within the Drupal community?
Bliss Media who are your preferred supplier and are working on our web refresh say this is a well used and recommended module. Also, your helpdesk engineer Shivan Jaikaran suggested this module would benefit the work we are doing currently.

** Additional information
Having worked as a web admin/front end dev for over 16yrs now, duplicating content is a basic feature on every CMS I have used (which is many). I understand GovCMS won't install new modules unless they benefit the masses and the introduction of this feature would greatly benefit all GovCMS editors as it will enable us to be more efficient and work smarter, not harder.
Having this added to our functionality would make a lot of users extremely happy - reading the Drupal community pages, users who didn't know of this and learn of it are all delighted they can now have a way to do this essential and important function.
It is more surprising that we don't have this function - I really hope it can be added to improve our ability to produce content in the most efficient way.

[thisisalistairsaccount]

Hi @sarahjames-ditc thanks for submitting.

I'll mark this as "requires more community feedback/interest". Those that are interested can leave a comment or react to your post to show interest/support in the module.

There's a few things that can be done without requiring the need to clone. Many elements and approaches to Drupal are designed to be reusable and if there's recurring elements or presentation you are after, then this is usually the best starting point.

Blocks are an approach that could present the same recurring information across a multitude of pages. These contain the same recurring information and can be set to reappear on the same content type, or certain URL patterns and other conditions. Where the information is the single source of truth, this is an approach that can be done once, edited in one place, but served to many different locations on a site.

At a content type level, where content is regularly re-used but may need the occasional change depending on circumstances, placeholder/default value content can be added to fields. For example, if you have a content type that talks to say a piece of legislation, you may have

Also at the content type level, fields can also be created and themed at the twig level to present in a certain manner. For example, if you are intending to included a reference to a video, you could create a field that allows you to enter say a YouTube link and then present it in a certain way on screen. Having a field like this means you could then render it in the same consistent way on screen across multiple content types. You can also create conditional elements at your template level to work in specific ways depending on what material has been added to a page.

Another approach could then be done with paragraphs to have a reusable field that could be added multiple times to a piece of content with the same fixed output. Applying the concept of the YouTube example above, having a paragraph that creates a location for you to add a YouTube video, means you could add multiple videos in a single page, ordered as needed.

The above approaches can be done with the GovCMS distribution right now with the right mix of content design, consideration around elements that you may or may not need, considerations for reusability and technical know how.

Happy to chat further on any of the above.

Cheers
Alistair

[larowlan]

Can I recommend replicate module?

[thisisalistairsaccount]

Hi @larowlan I think Replicate https://www.drupal.org/project/replicate might be a better option, noting the slightly bigger scope than just content nodes. Might be best we create a new issue for that and gain interest from there

[larowlan]

Added #867

[StephenOllman]

Do we know if ths works if nodes also using paragraph fields (components), as this is where I can see this functionality being really useful?