Enhance the Text Content for Better Engagement on Html Sanity Check (HSC) Page

[Shreyhac]

The current text content on the Html Sanity Check (HSC) page is informative but lacks an engaging tone. Updating the language to make it more compelling can help capture user interest and make the project more approachable. This will ensure users not only understand the purpose but are also excited to try out the tool.

Suggested Changes:

Introduce a Catchy Tagline:

Current: "This project provides some basic sanity checking on HTML files."
Suggestion: "Keep Your HTML Spotless with Html Sanity Check (HSC) – Your Go-To Solution for Error-Free Code!"
Make the Description More Enthusiastic:

Current: "It can be helpful in case of HTML generated from e.g. Asciidoctor, Markdown, or other formats - as converters usually don’t check for missing images or broken links."
Suggestion: "No more missed errors in your HTML! Whether you’re generating HTML from Asciidoctor, Markdown, or other formats, HSC has your back. It ensures every image is in place and no link is left broken, giving you peace of mind with every build."
Highlight the Versatility:

Current: "HSC can be used programmatically or as a Gradle plugin. A standalone Java command line interface (CLI) version is planned as well as a Maven plugin for future releases."
Suggestion: "Use HSC however you like—whether it’s programmatically or through a Gradle plugin. And there's more! A standalone Java CLI version and a Maven plugin are on the horizon, offering even more ways to integrate HSC into your workflow."

[ascheman]

This sounds like a great idea, thanks for bringing this up, @Shreyhac. Would you like to work on this topic in the course of this years Hacktoberfest? I'd appreciate if you could polish some of the documents with your obvious writing skills.

To be honest, since I took over the project I didn't find much time to look into the documentation. Perhaps I even wrote new documentation fragments in the very same style as the old ones?
However, I think there are even more flaws as the code (and in particular the architecture) was refactored. Hence, the documentation needs to be aligned with the current and upcoming code changes. We already have some code for Maven (#314) and CLI (#318) in the pipeline, as well as a documentation update wrt. to architecture graphics (#326).

[Shreyhac]

hey@= @ascheman i would love to work on this , please assign me this under hactoberfest

[ascheman]

Thanks a lot, it is assigned to you.

Are you on (the Hacktoberfest) Discord? You can reach out to me (gerdaschemann) so we could have a chat if you need any other support.