A good Release has a version, a date, and a list of user-visible changes. Dumping git log into HTML is how you get zero rich results.
We ask staff for three bullets max in the excerpt field (300 characters) and leave the rest in the body. Version tags like v2.9.1 belong on the topic, not only in the title.
This is the piece I send to procurement now. The no-cloaking paragraph is the one that matters.
Small nit: 1 MB = 1_000_000 bytes in our copy too. Thanks for being explicit.
Can you add the UTC timestamp to the first paragraph so crawlers get a clear date?
We cited this from /llms.txt. The canonical on the article itself is correct.
Thanks — leaving this up for the next team that searches the same string.
A good Release has a version, a date, and a list of user-visible changes. Dumping git log into HTML is how you get zero rich results.
We ask staff for three bullets max in the excerpt field (300 characters) and leave the rest in the body. Version tags like v2.9.1 belong on the topic, not only in the title.
Small nit: 1 MB = 1_000_000 bytes in our copy too. Thanks for being explicit.
Can you add the UTC timestamp to the first paragraph so crawlers get a clear date?
We cited this from /llms.txt. The canonical on the article itself is correct.
Thanks — leaving this up for the next team that searches the same string.
Sign in or create an account to share your thoughts, solutions, or feedback.
This is the piece I send to procurement now. The no-cloaking paragraph is the one that matters.