-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixed formatting, spelling, grammar and added seo metadata to all pages #107
Conversation
…mar. Changes: - Added seo metadata such as title and description to all the valid pages. - Fixed broken links. - Fixed formatting, spelling and grammar.
@oleg-nenashev do you think we can add Gradle Build Server to https://github.com/gradle/community/pull/107/files#diff-3f5a2bbb87f30238aee5f0305a6849725d63604134f87d5a4264c78e9af0f67b? |
There is also different closing tag in community/overrides/resources.html Line 9 in 5619030
community/overrides/resources.html Line 14 in 5619030
Is that intentional? |
No objections about adding Gradle Build Server. We do not yet have rules
set for managing this list, so it's based on contributions.
Regarding the headers, it's definitely a typo by me
…On Mon, Oct 7, 2024, 17:32 Tanish Ranjan ***@***.***> wrote:
There is also different closing tag in resources.html:
https://github.com/gradle/community/blob/5619030a18fe13ac38848f5946f2d68b22c22a3a/overrides/resources.html#L9
https://github.com/gradle/community/blob/5619030a18fe13ac38848f5946f2d68b22c22a3a/overrides/resources.html#L14
Is that intentional?
—
Reply to this email directly, view it on GitHub
<#107 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAW4RIG452XHWZPSC64QOOLZ2KSQHAVCNFSM6AAAAABPQGHZZCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJXGI2TQNJXGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
*
CONFIDENTIALITY NOTICE*: The contents of this email message, and any
attachments, are intended solely for the addressee(s) and may contain
confidential, proprietary and/or privileged information legally protected
from disclosure. If you are not the intended recipient of this
communication, or if you received this communication by mistake, please
notify the sender immediately and delete this message and any attachments.
If you are not the intended recipient, you are hereby notified that any
use, retransmission, dissemination, copying or storage of this message or
its attachments is strictly prohibited.
|
Changes: - Added Gradle Build Server to projects readme. - Added links to all the mentioned projects in projects readme. - Fixed closing html tag in resources.html
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is what happens when Grammarly disables SDK for VS Code :(
@@ -35,10 +35,10 @@ For other cases, other channels might be preferable: | |||
|
|||
1. If you suspect a security issue in Gradle Build Tool, plugins, its infrastructure, or other components, | |||
please avoid discussing it in public. | |||
Follow the [Gradle Vulnerability Disclosure Policy](../dotgithub/SECURITY/README.md) so that we can triage the issue and protect other Gradle users. | |||
3. If you want to report a confirmed and reproducible issue with Gradle Build Tool or other component, | |||
Follow the [Gradle Vulnerability Disclosure Policy](dotgithub/SECURITY/README.md) so that we can triage the issue and protect other Gradle users. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's still not fixed, I will patch it in my next PR. I think the correct path would be ../../dotgithub/SECURITY/README.md
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. I will deploy the checker for the site, I think it is quite stable at the moment
This PR fixes formatting issues, spelling and grammar throughout documentation of the repository and adds seo metadata to all the valid pages effectively completing #100