Cleaning up and correcting the project page [#3103800]

Please consider to change the project page content to get listed correctly in the module search and to not shy away users by reading this info text.

First part

Page Specific Class
================

This part is not needed and wastes space in the listing and search previews of drupal.org. There is already a project title on top. Apart from that consider renaming your project to "Page specific body class".

Second part

It is a simple module for Drupal 8 users to add custom CSS class to the <body> tag of the any specific page

Do not double comment your project regarding core version and project type (module) in the description. This can be seen on the bottom and in the preview and search listings.

Just shortly explain its features in a clear summary like:

Ability to add HTML attribute classes for CSS styling to the <body> tag based on path conditions like commonly known on the Block layout configuration pages. Specify body classes for pages by using their paths. Enter one path per line. The '*' character is a wildcard. An example path is /user/* for every user page. <front> is the front page.

Third part

Features

    We can add class to body tag of any page
    Support all Pages which can be created via Node, Views or Custom Route
    We can add class for Home page also
    We can add class for All pages also

Do not use "We"... and use HTML headings and lists.

Example:

<h3>Features</h3>
<ul>
  <li>Add different classes to the body tag of any page.</li>
  <li>Supports all pages which can be created via nodes, Views or custom routes, including home page.</li>
</ul>

Fourth part

How to use?
=======
For how to use this module please go through README.txt file. It's very easy and straight forward.

Do not tell the user how easy it is, because this is very subjective. Just make note about the README or use some standart formulation about the installation methods. Consider linking to the module installation documentation pages on drupal.org - Examples can be seen on other project pages what users are used to read here.

The project page could look like this (copy/paste):

Ability to add HTML attribute classes for CSS styling to the <body> tag based on path conditions like on the Block layout configuration. Specify body classes for pages by using their paths. Enter one path per line. The '*' character is a wildcard. An example path is /user/* for every user page. <front> is the front page.
<h3>Features</h3>
<ul>
  <li>Add different classes to the body tag of any page.</li>
  <li>Supports all pages which can be created via nodes, Views or custom routes, including home page.</li>
</ul>
To learn more about the project and how to install and use it check out the README.txt (use a link here). Feel free to report issues and by helping on the documentation pages,

Demo view

Ability to add HTML attribute classes for CSS styling to the tag based on path conditions like on the Block layout configuration. Specify body classes for pages by using their paths. Enter one path per line. The '*' character is a wildcard. An example path is /user/* for every user page. is the front page.

Features

Add different classes to the body tag of any page.
Supports all pages which can be created via nodes, Views or custom routes, including home page.

To learn more about the project and how to install and use it check out the README.txt (use a link here). Feel free to report issues and by helping on the documentation pages,

Comments

Comment #1

31 December 2019 at 03:54

diqidoq created an issue. See original summary.

Comment #2

dqd

(formerly "diqidoq")

CreditAttribution: dqd as a volunteer and at MAROQQO studios commented 31 December 2019 at 03:57

Issue summary:

View changes

Comment #3

dqd

(formerly "diqidoq")

CreditAttribution: dqd as a volunteer and at MAROQQO studios commented 31 December 2019 at 04:00

Title:	Cleaning up the project page	» Cleaning up and correcting the project page
Issue summary:	View changes

Comment #4

dqd

(formerly "diqidoq")

CreditAttribution: dqd as a volunteer and at MAROQQO studios commented 31 December 2019 at 04:43

Additionally another kindly suggestion which should not discourage: it is recommended to add a list of projects with a similar or nearby attempt to compare them, like:

Similar projects with different attempts:

Custom Body Class (very similar but buggy)
Body node ID class
Extra body classes

For copy/paste here in code tags:

<h4>Similar projects with different attempts:</h4>
<ol>
  <li><a target="_blank" href="https://www.drupal.org/project/custom_body_class">Custom Body Class</a> (very similar)</li>
  <li><a target="_blank" href="https://www.drupal.org/project/body_node_id_class">Body node ID class</a></li>
  <li><a target="_blank" href="https://www.drupal.org/project/extra_body_classes">Extra body classes</a></li>
</ol>

Did the project maintainer knows that there is already an older module contributed and sponsored by the same company QED42 here on drupal.org with a slidely different feature set (the third one above) Development version: 8.x-1.x-dev updated 19 May 2016 at 12:27 UTC ? And the first one on the list is very similar but has some dangerous bugs https://www.drupal.org/project/issues/custom_body_class?categories=All&s...

I think this will be another issue to discuss regarding merging forces. It would be great to have one project for all body class options and not several modules for each option.