Create a short description (200 characters or less) that will be easily understood by the Project Browser target audience of site builders and those new to Drupal. The short description should answer the question - "what does this module do in a non-technical way".

MAINTAINERS: the short description should be added to the Summary field of the Description on the project page. The short description will be displayed on the cards in the Project Browser grid and list views.

Proposed Resolution

Helps frontend developers get partial data from Drupal field render arrays, so they can better control the output without using preprocess functions.

Comments

volkswagenchick created an issue. See original summary.

David Vallance’s picture

Can you elaborate on this requirement please?

urvashi_vora’s picture

Assigned: Unassigned » urvashi_vora

@David Vallance,

As per Parent Issue: https://www.drupal.org/project/project_browser/issues/3282985

The short description should answer the question - what does this module do in a non-technical way.

This issue is about adding a short description. We can suggest a few sentences about what the module is actually doing in non-technical terms.

Assigning it to myself, will suggest something.

urvashi_vora’s picture

Assigned: urvashi_vora » Unassigned
Status: Needs work » Needs review

According to me,

I'd use any short description found in the documentation.

How about??

Twig Field Value module helps the frontenders to get partial data from Drupal field render arrays. It gives them more control over the output without using preprocess functions. It can be used to create single or multiple field values such as content.

Marking it to Needs Review.

Please provide your valuable feedback.

Thanks

David Vallance’s picture

Thank you for your feedback. I have entered your suggestion urvashi_vora and marked as fixed.

Let me know if this was not the correct approach to this.

David Vallance’s picture

Issue summary: View changes
Status: Needs review » Fixed
urvashi_vora’s picture

Hi David,

From the knowledge which I have is, a issue should ideally move to RTBC (Reviewed and Tested by Community) from Needs Review if the changes looks good, ideally. If no, then to Needs work, and once we have RTBC issue status, then it's the module maintainer's call to mark the issue as fixed.

Correct me if I wrong.

Thanks

volkswagenchick’s picture

Status: Fixed » Needs review

Moving this back to needs review.
@urvashi_vora - you are correct with the workflow.

Marking as fixed is left to maintainers of the specific issue queue.

urvashi_vora’s picture

Thanks @volkswagenchick

adrian_s_m’s picture

Status: Needs review » Needs work
Issue tags: +MidCamp2023

I would remove this part "It can be used to create single or multiple field values such as content." from the proposed resolution since there is no mention of that in the readme.md or the description of the module here Twig Field Value.

adrian_s_m’s picture

Status: Needs work » Needs review

Proposed resolution:

Twig Field Value module helps the frontenders to get partial data from Drupal field render arrays. It gives them more control over the output without using preprocess functions.

chrisfromredfin’s picture

chrisfromredfin’s picture

Issue summary: View changes

Phrased more simply:

Helps frontend developers get partial data from Drupal field render arrays, so they can better control the output without using preprocess functions.

I like saying "developers" right there in the quick description for developer-only modules, too.

ebremner’s picture

I agree that this short description fits for this module, which is a great module.

ebremner’s picture

Status: Needs review » Reviewed & tested by the community
leslieg’s picture

Status: Reviewed & tested by the community » Fixed

Assigned credit and marked as fixed.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.