Active
Project:
Paragraphs
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
21 Dec 2016 at 10:41 UTC
Updated:
21 Apr 2022 at 21:56 UTC
Jump to comment: Most recent
Problem/Motivation
We started to analyze the Paragraphs ecosystem to gain overview and maximise the value of the energy spent.
This is our blogpost with the call for collaboration
https://www.md-systems.ch/en/blog/business/2016/12/19/lets-collaborate-f...
Proposed resolution
This issue is a common reference point for all issues created in the related projects.
Comments
Comment #2
miro_dietikerComment #3
miro_dietikerConnecting with the roadmap.
Comment #4
kirkilj commentedAs a new developer to Drupal with a deadline to hit for my first Drupal-based solution and a lot of confusion about the Paragraphs ecosystem, I'm pleased to see efforts to collaborate and keep the Paragraphs ecosystem from splintering out of control. I was pleased to see that someone had bundled up a Bootstrap solution for Paragraphs. It is a bundled solution to a set of requirements I have, but was dismayed to see that it required custom paragraph types. When I'd look at the paragraph type list after installing several Paragraphs related modules, such as Paragraphs Base and Paragraphs Collection, there appeared to be a lot of duplication, based purely on the paragraph type names as well as their presentation and functionality. I'm encouraged by the architectural work being done on a new Plugin system for Paragraphs.
I also just saw some nice tweaks to the Paragraphs UI provided by the Paragraphs Extras module, but that's just D7 with no current plans for D8 from what I can tell.
I've heard that this has been debated in other corners, but the name "Paragraphs" drives me nuts, since these are much more than Paragraphs. I think of them as components or elements, but that's just me being picky. I'm sure the Drupal module namespace is full of useful names that are already spoken for and a rename refactor at this point could be a major undertaking and affect other modules. I'll need to make sure this name is not exposed to editors.
Great work Miro and other module developers for addressing the collaboration and refactoring issues. If my D8 API and PHP OOP skills were much further along, I'd jump into the fray. The Paragraphs Trello board provides transparency and allows me to see where things are heading and what's being worked on actively.
Comment #5
spidersilk commentedSome of the things that are currently in add-on projects seem like they really ought to be part of Paragraphs itself - notably, Classy Paragraphs and Paragraphs ID. Having classes and IDs that can be used for theming shouldn't be an optional add-on, or require using possibly unstable modules that are not covered by the security advisory policy - that should really be a basic feature!
Comment #6
miro_dietiker@spidersilk these topics you mention either have their issue already or are need a specific issue to discuss.
Mind that we do not want to clutter the ui with technical drupalism features. Pararaphs is about maximising the UX for content creation. Also there is a new plugin system that allows for a new dimension for extensibility that can be used to implement such things. We propose experimental approaches to common needs in Paragraphs Collection and we consider adding parts from there to Paragraphs over time when we decided about a stable approach.
That said, this issue is about collaboration, not collecting requirements. Please pick an issue, create one, take ownership, make a more detailed proposal, talk to us, contribute or fund our work through such a feature. It's the moment to help us make things happen. How did you intend to contribute?
Comment #7
a.milkovskyUpdated the blogpost link.