Improve Block Class's project page

I assume we could probably try improving the documentation of the module, since it has changed so much...
I mean, at least we should be moving the Drupal 6 snippets elsewhere...
Especially with Drupal 8 upon us, we should definitely be updating the documentation.

On top of that we have to deal with compatibility with popular themes such as Bootstrap → (see #2125947: Bootstrap Users: note that NO block.tpl edits are required → ), Zen → (see #2124659: No PHP snippet required with Zen theme 7.x-5.4 → ) or Omega → (see #2453577: Does not work with OMEGA framework (and others) → ).
Ideally, we could also try to make a more prominent statement about why users like using Block Class, as an attempt to answer #1964944: What are the technical merits of Block Class? → .

Below are some ideas for some areas of improvements around the documentation of the module:
See also the Block Attributes → module's project page

Project page, could be a little bit more detailed:

1 - Project page description:
We could certainly add more information about the module's configurations.

• Introduction: one liner to let users know what this module does (200 chars max).
• Features: what the module can do.
• Implementation: how the module does what it does.
• Troubleshooting (Known Theme issues): this is a key section where we might be able to squeeze all outstanding theme related issues, bootstrap, omega, zen and all other ones.
• Important! Installation and usage paragraph: how the module should be installed and configured.
• Review recommendations at: Project page template → , Module documentation guidelines → , Tips for a great project page, Best practices for creating and maintaining projects → and README Template → .
• Similar projects: other modules that do more or less the same things as this one.
• Many other sections: see the sections suggested by the Project page template → , README Template → and Tips for a great project page documents, for example, Troubleshooting, Known issues, Future developments, etc...

2 - Screenshots:
Consider adding screenshots that could demonstrate module's functions:

• Backend settings of a block's configuration CSS classes highlighted and annotated.
• Front end display of the classes in a browser inspector.

Feel free to let me know if you would have any comments, feedback, questions, issues, objections, suggestions, additions or concerns on this task, I would surely be glad to provide more information or explain in more details.

Thanks in advance to everyone for your testing, reviews, feedback and comments on this issue.
Cheers!