Define guidelines and process for Badge usage, specially "New"

          > Also I couldn't find any guidelines, on the Badge New, on how it should be used and how long something is considered new.

For now I just said 6 Months in Contributing.md, but that's just a place holder. That's something, which requires multiple peoples input.

Say this guideline receives approval. How to enforce it?
I have a reminder set in my calendar, but that's not solution, I suppose.

So, have a file (eg. .github/Bage-Lifetimes.md) with the dates of when the badge should be removed?

# Removal Dates

List of files and dates, on which the `New` badge should be removed.
| Directive           | Description                                        |
| ------------------- | -------------------------------------------------- |
| Order               | Insert so, that the next removal is always on top. |
| Date Format         | `YYYY.MM.dd`                                       |

- [`http-headers.mdx`](../src/content/docs/security/http-headers.mdx): 2025.05.13

Or is there some CI workflow for notifications or something like a delayed commit. Both of these come with their own set problems and considerations.

Originally posted by @39zde in https://github.com/tauri-apps/tauri-docs/issues/2950#issuecomment-2473526540

Review the Badge New discussion in Contributing.md and the proposed .github/Badge-Lifetimes.md process. First inventory how the New badge is currently used, then gather the multiple stakeholders' input on its lifetime and enforcement. Done means the project has an approved guideline and a clearly chosen maintenance or CI process.