[META] Roadmap to a 2.0.0 release

I am considering using Layout Paragraphs for an upcoming project, but some of the developers working with me have concerns about starting a project with v1 of the module and later having to transition to v2. What is the expected upgrade path to v2? Is it intended to be relatively straightforward? Should we wait until there is a full release of v2? Any information would be helpful to us in making a determination about how to proceed.

@gabesullice and @justin2pin, thank you very much for your hard work on 2.x. I have the same question as @aaronpinero and hope there will be a 100% upgrade path. Is that correct and to be expected?

Any updates on the 2.x branch? Can we perhaps help to push things forward? I think this project is VERY important for Drupal at all and I'm wondering if there shouldn't be further resourced available for help from the Drupal Community. Paragraphs benefits a lot from this project!

Does this project only have 2 (but great) maintainers / developers: itamair + justin2pin?

Hey all - thanks for this. Here are a few comments / updates:

- First, importantly, YES there will be a simple upgrade path from V1 to V2. The underlying storage isn't changing at all. V2 introduces a number of APIs that other developers will be able to leverage for building modules with a broad range of add-on capabilities. V2 is a complete re-write, but drastically simplifies and improves the underlying code architecture. To upgrade, developers will simply need to switch to the new branch and clear caches.

- To reach 2.0.x Stable, we just need a complete suite of automated tests. The framework is in place, and there are a couple tests already added. I'd like to see automated tests written for all aspects of the module. So... if anyone wants to contribute additional tests, that would be a fantastic way to push this forward!

Thank you for the update. This is really great to hear. My experience so far with Layout Paragraphs has been really good and I think this is an excellent solution for providing content creators with better tools.

Unfortunately, I don't really have the ability to contribute to code tests -- I am only a front-end developer. But I just want to say thank you for all the work on this module.

I've been building on the V2 for an upcoming site. I first explored the V1 and noticed that paragraph behavior forms are not currently implemented in V2.

I created ticket #3229555: Add Paragraph Behaviors Form Support for that feature.

I hate to ask this -_- But could anyone give an update of the current state? Is there a rough time window you have in mind?

We plan to migrate a huge site to Layout Paragraphs, and we try to figure out if it makes any sense to wait for 2.0 stable.

Hi @justin2pin,

I just reviewed and commented some issues that might be relevant here, please have a look.

Also I guess a clarification in some 1.0.x issues might help about further development (switching the issues to 2.x) if there is no plan to put further maintainer time into 1.x, which would make sense, as I guess.

Perhaps also add a sentence like

1.x branch will not receive further (feature) development. Further development will happen in 2.x. Please help (see below)

on the module page and close (irrelevant) / switch over (relevant) 1.x issues?

These are possibly relevant 2.x issues for the list above (important):

Possible bugs / feedback:

#3216981: All buttons being moved into modal actions
#3252978: Large modal exceeds viewport height without scrollbar = actions unreachable
#3228835: form-actions styles leak into paragraphs containing forms
#3253875: hook_layout_paragraph_element_form_alter not existing
#3223849: Provide layout info in hook_preprocess_paragraph
#3240086: Unable to remove paragraph added from Paragraphs library
#3230080: Use moveError validation for up and down arrows in addition to drag and drop
#3249006: Field template is missing with edit in-place.
#3200236: Module is not working for all layouts
#3218949: Javascript isn't compatible with html button
#3283720: Javascript error - Uncaught ReferenceError: dragula is not defined
#3276855: Passing null to parameter #1 ($string) of type string to mb_strtolower() is deprecated

Usability:

#3254892: Improve UI / UX for (Un)published
#3244687: Improve usability for moving paragraphs between regions.
#3202220: If there is only one layout paragraph the widget should autoselect it
#3223474: Improve Styles
#3265669: Show loading spinner at layout selection, otherwise may select wrong layout (UI race condition)
#3297025: Edit buttons not accessible on small layouts or screens (responsiveness)

Features:

#3218226: Cloning Entities containing Layout Paragraphs breaks structure (cloning)
#3246421: Improve organization of tests (tests)

Documentation:

#3189502: Project page Getting started steps are inadequate
#3205312: Link layout_paragraphs_restriction module

Perhaps split off a 2.1.0 release plan, for example with (nice to have's):

#3195510: Support default layouts and content for layout paragraphs
#3208180: Provide frontend editing experience for Layout Paragraphs.
#3231747: Add possibility to use layouts with paragraphs-experimental field widget
#3158244: Improve the content editor experience
#3166362: Add setting to limit what paragraph types can be in section layouts.
#3197059: Setting whether admin or front-end theme is used for paragraph edit forms
#3224488: Add ability to adjust column widths with widget UI

What do you think?

Hope I was able to structure and help you a bit... :)

I'm keen to get Layout Paragraphs 2.x into LocalGov Drupal distribution, the UX is so much better, thanks for your amazing work!

If we can find time to help with some of the issues towards a stable 2.0.0 release, we will.

With this in mind, it would be good to confirm which of the issues in Anybody's comment above are blockers to a release. Perhaps we could update the issue description with the important issues?

Updated the issue summary with the suggestions from #14 and updated the list.

@justin2pin? As 2.0.0 is out, this could be set Fixed or Won't fix. Anyway it would be cool, if you could look through the listed issues.
For example, #3297025: Edit buttons not accessible on small layouts or screens (responsiveness) is major, I think.

Thanks a lot!

Maybe it's a good idea to add the restriction of paragraph types to certain regions as a feature for the 2.x release (or 2.1+)?
This feature would greatly improve the useability of the module for projects with a large sum of paragraph types.

At the moment this is linked under Documentation, but the paragraphs_restriction module is only supporting the 1.x branch of this module.

@Anybody - thanks for your comment in #20. I'm going to leave the title on this one as it was and flag as fixed (as you recommended), since this issue was really just about getting to a stable 2x release. I'll post something separate -- either as a meta issue or in documentation -- about releases moving forward.

Is Support revisions and content moderation with the Layout Paragraphs Builder Field Formatter on your radar?

+1 on #25