Problem/Motivation

As follow-up on #3034248: Promote use of Token Or module to make tokens more flexible I'd like to vote for adding a list of helpful contrib modules on the module page and in the README to help users solve typical problems.

Here's my list of suggestions:

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

CommentFileSizeAuthor
#12 metatag-n3552557-12.patch3.31 KBdamienmckenna

Issue fork metatag-3552557

Command icon 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:

About issue forks

Comments

anybody created an issue. See original summary.

anybody’s picture

anybody
Primary language German
Location Porta Westfalica
commented
Issue summary: View changes
jwilson3’s picture

jwilson3
Primary language English
Location Ecuador
commented

+1. To be helpful, each module needs a super-brief description of what problem it solves in the context of Metatag module. In the case of the ones that extend token logic a brief example of the syntax would be really helpful too. Maybe it makes sense as a docs page instead?

anybody’s picture

anybody
Primary language German
Location Porta Westfalica
commented
Issue tags: +Novice

Yes I agree. A docs page is less visible maybe, so I'd prefer the module page, but not my decision.

I think this is a nice novice task to prepare...?

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Title: List helpful additional modules on the module page (and README?) » List helpful additional modules on the module page and README.md
Issue summary: View changes

Given that in gitlab the README.md file will become the project page's description, the README.md needs to be updated too.

jwilson3’s picture

jwilson3
Primary language English
Location Ecuador
commented

We should also leverage the Metatag ecosystem https://www.drupal.org/project/metatag/ecosystem

  • Expand the list in the IS to include everything classified in the metatag ecosystem.
  • Open issues in more modules (eg "Token Or", and others) to add the Metatag ecosystem to their respective project edit forms.

Re: novice task - Makes sense. Writing up the relevant description for each module (as I suggested/requested in #3) might be the harder part, but an appropriately prompted LLM could probably take a first stab.

priyansu18 made their first commit to this issue’s fork.

priyansu18 opened merge request !221

priyansu18’s picture

priyansu18 commented
Status: Active » Needs review
priyansu18’s picture

priyansu18 commented

Hi, is this documentation okay?

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Parent issue: » #3548158: Plan for Metatag 2.2.1
damienmckenna’s picture

damienmckenna
Location TN, USA
commented
StatusFileSize
new metatag-n3552557-12.patch3.31 KB

The README.md file already includes a section of "Recommended / related modules", so the new items should have been listed there.

This is what I thinking of, and thanks to jwilson3 for suggesting the ecosystem page.

  • damienmckenna committed 66e99819 on 2.2.x 
    Issue #3552557 by anybody, jwilson3, damienmckenna, priyansu18: List...
damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Status: Needs review » Fixed

Committed, and I updated the project page. Thank you.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

damienmckenna closed merge request !221

Status: Fixed » Closed (fixed)

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