Improve project description

I'll take a stab at a first draft.

Updated issue summary with a start.

Added detail about CRM Core

We should avoid using a header at the top of the description to help with Project Browser initiative ( 📌 [Meta] Create a short description for a contrib module Active ). I would avoid using the Summary field because text_with_summary is proposed to be deprecated from core.

Architecture section may be better suited to a CONTRIBUTING.md or DEVELOPERS.md file or gitlab pages.

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.

@mradcliffe Thanks for reviewing.

I'm inclined to leave the architecture piece where it is for the time being as it might be the first question some evaluating the project will have. It's also a key differentiator.

I'm confused by "I would avoid using the Summary field" along with "the short description should be added to the Summary field of the Description on the project page", which seem to conflict.

If we use the summary field for the short description, can we safely use headers in the rest of the description?

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