Add Drupal 'keywords' to Recommended Drupal project composer.json, and update description

Rassoni → made their first commit to this issue’s fork.

Rassoni → closed merge request !3835

Thanks @Rassoni, I think that looks great. To me, it looks ready to get committed, but let's maybe wait and see how the community feel about it. Have a nice day!

Change seems simple enough and updates make sense. Wonder how long that Drupal 9 keyword will be needed though.

Thanks for a fast response @smustgrave. And yes, maybe we should just drop "Drupal 9"?

Regarding improving the Composer package experience, there's also 📌 Add README.md to composer project templates Needs work . It's only mentioned here, but I think expanding the README.md in line with for example palantirnet/drupal-rector would make the Recommended page rank better in a search for "Drupal" on Packages.org. What do you think?

I don't know why they text on packagist is not displaying the latest description.

Thanks for taking a look at it @quietone. It make sense to not include specific versions, but can't we at least add "Drupal" as a key word?

    "keywords": ["Drupal"],

That should be low maintenance :)

@quietone:

... text on packagist is not displaying the latest description.

Maybe because it pulls it from the default version of https://github.com/drupal/recommended-project which is currently 9.1?

Setting it to be the current official release 10.0 could fix it: https://github.com/drupal/recommended-project/tree/10.0.x

Publish It

[...] Once you entered your public repository URL in there, your package will be automatically crawled periodically. You just have to make sure you keep the composer.json file up to date.

From https://packagist.org/

If this is true, then changing default version to the current official release should probably be added to the checklist of tasks, when minor versions of Drupal (10.1, 10.2, etc.) are released every half year or so.

Generally speaking, it's also just good practice. I realized the importance of this during the updating of plenty of README.md's the last few months, to make sure show the latest updated version is used :)

I have created #3355085: Set default version to latest official release on github.com/drupal → .

Going to remark it and see what the committer things for

"keywords": ["Drupal"],

I asked about the packagist description in #composer and #hestenet has updated it.

Before setting an issue to RTBC it is useful to check that the issue Meta data is correct. This helps the next reviewer/committer to select what to work on. For this issue, the title is not correct and is misleading to others. Per List of issue fields → the title is "A description of what the issue is intended to resolve.". It is also used for the commit message and having it correct is useful when people search the git log in the futur

Great that the description has been updated on packagist.org, @quietone.

Do you know if @hestenet updated the description directly on packagist.org, or if it pulled the data from https://github.com/drupal/recommended-project after the default branch was updated from 9.1 to 10.1 yesterday?

Since description and keywords are still both in play, it would make sense to add keywords but also keep description in the title, I think.

What is you opinion on adding "keywords": ["Drupal"], in composer.json?

Unsure if it is the right issue, but if you could change the About description on GitHub of https://github.com/drupal/recommended-project that would be great too. Confused me for a while.

It states the following:

> About
Project template for Drupal 8 projects with a relocated document root

While it is for more recent Drupal versions as well.

Good catch @wwalc, I never noticed that before.

If you're interested, there's an issue about adding a README to that repository, 📌 Add README.md to composer project templates Needs work .