Problem/Motivation
Trying to understand basic configuration.
Steps to reproduce
Reading: "Go to your content type and add a new field of type Entity revisions, Paragraphs."
Uncertain what the meaning of this statement is. Default fields available for content types are similar, but no exact match found. E.g.
Entity reference revisions field type is available but not Entity revisions, Paragraphs
Proposed resolution
Kindly clarify the intent of this instruction
Remaining tasks
User interface changes
API changes
Data model changes
Issue fork uswds_paragraph_components-3352988
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
axbWith experimentation I discovered that Content type > Add field > Add a new field > - Select a field type - > Reference revisions - Paragraph seems to map the field to a type that can be used to create at least the USWDS Cards (Regular) component. This shows in the table as Field type: Entity reference revisions - which I think is what was intended by the configuration instructions.
Comment #5
smustgrave commentedThanks for reporting. This was one of my first drupal modules so happy to see it's used.
Updated the README with some details. Let me know if that makes more sense.
Comment #6
axbThis is great. I can take a closer look when I get in to the office today.
I'd be happy to help write documentation for this module. It seems like it will be a useful addition to our project.
> "Go to the content type you wish to add the paragraph components too."
Could be further rewritten for clarity as:
> "Create or edit the relevant content type in your Drupal project."
This shortens the word count and avoids the preposition "to" at the end of the sentence.
I can also make a try at contributing documentation changes through the issue system, if needed.
Comment #7
smustgrave commentedSay go for it.
Comment #8
axbMade a trivial commit. My first commit to Drupal code. I will look for additional opportunities to contribute here.
Comment #10
smustgrave commentedThanks! And highly encourage any feedback or change requests!
Comment #11
smustgrave commentedThis actually should of been marked fixed.
Comment #12
smustgrave commentedComment #13
axbThank you again. We are currently implementing page layouts using this module. It seems like it will be very useful for us, and it looks like more people are trying it out recently. I will keep an eye out for opportunities to contribute as I become more familiar with it.