WIP: Basic structure for showcasing community contributions

[cwognum]

Checklist:

• [X] Was this PR discussed in a issue? It is recommended to first discuss a new feature and let the community know whether you are planning or have started working on it before opening a PR.
• [ ] Add tests to cover the fixed bug(s) or the new introduced feature(s) (if appropriate).
• [X] Update the API documentation if a new function is added or an existing one is deleted.
• [x] Added a news entry.
  • copy news/TEMPLATE.rst to news/my-feature-or-branch.rst) and edit it.

---

ping @maclandrol. I proposed a basic structure so we can discuss! What do you think?

[cwognum]

For now, I was thinking of having a table with a row per contribution that links to an external page (e.g. Github of a plugin, blog post, etc.). Or would you prefer copying as much as possible over to molfeat instead of having a link?

[maclandrol]

For now, I was thinking of having a table with a row per contribution that links to an external page (e.g. Github of a plugin, blog post, etc.). Or would you prefer copying as much as possible over to molfeat instead of having a link?

No, the table is perfect. We can also add some links or some badges in the original tutorials too.

[maclandrol]

Also ping @zhu0619

[cwognum]

@maclandrol I addressed your comments! The community contributions page probably still needs some context descriptions, but I'll do those later. ~In the meantime, could you add the IPU badges? I cannot see the raw README and thus cannot copy the IPU badge (I saw you edited the description, so you probably can?).~

[cwognum]

Reference in existing documentation:

New community contributions table