The old picker said Feature Request and Bug Report. Faculty read that as "this product is for GitHub people".
Renaming to Idea and Issue, then adding Article, Guide, Event, and Job, let a registrar post without translating our jargon.
We still hide staff-only templates from members. The picker is denser, but the first choice is always the one they need.
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.
The old picker said Feature Request and Bug Report. Faculty read that as "this product is for GitHub people".
Renaming to Idea and Issue, then adding Article, Guide, Event, and Job, let a registrar post without translating our jargon.
We still hide staff-only templates from members. The picker is denser, but the first choice is always the one they need.
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.