Enhancement: Consistently use composer package name for link content

[localheinz]

This PR

• consistently uses the composer package name as link content for links to 3rd party libraries

💁‍♂ I'd also suggest

• consistently liking to GitHub repositories (rather than in at least one example, linking to https://packagist.org)
• perhaps removing abandoned packages
• splitting the list (perhaps into sections Framework Integrations and Providers)
• keeping the list(s) sorted by package name

We could also start adding GitHub issue and pull request templates, and add a template for adding a library that gives suggestions, what do you think?

[pimjansen]

@localheinz agree with all the bullets. I think the templates could really help. Also the template how to report a bug since we miss a lot of code snippets and such.

Will you take that in this PR or split it up?

[localheinz]

@pimjansen

Personally, I'd prefer to keep the scope of pull requests limited to one change - what do you think?

[pimjansen]

@pimjansen

Personally, I'd prefer to keep the scope of pull requests limited to one change - what do you think?

Totally agree, was just wondering since you commented it here. So this PR further looks ok!

[fzaninotto]

I'm OK for all, except

• removing abandoned packages

We can't commit on regularly checking if all those packages are still maintained.

[fzaninotto]

Sorry, wrong button

[localheinz]

Thank you, @fzaninotto and @pimjansen!