Proposal: Cleanup policy for legacy, inactive, and archived repositories

[CristhianDaza]

Description

I would like to start a discussion regarding the current status of some resources in the list. To maintain the high quality and relevance of awesome-vue, I propose identifying and potentially removing items that meet the following criteria:

1. Vue 2 Only: Resources that haven't migrated or don't support Vue 3.
2. Inactivity: Repositories that haven't been updated in 2 or 3 years.
3. Archived Status: Projects that are officially archived by their authors on GitHub.

Motivation

As the Vue ecosystem continues to evolve with Vue 3, keeping legacy or unmaintained links might be misleading for developers looking for production-ready solutions. A "cleaner" list would improve the developer experience and ensure the resources provided are reliable.

Proposed Action

I am willing to help audit the list and flag these repositories. However, I would like to hear the maintainers' thoughts first:

• Should we remove them entirely?
• Should we move them to a "Legacy/Archive" section?
• Is there a specific threshold for "inactivity" (e.g., 3+ years)?

I'd love to hear your feedback on this!

[Jogai]

Sure. Though I'm just helping out, not the main maintainer. Vue 2 only stuff is maybe nice to move to a readme-vue-2.md? The rest could go imo

[CristhianDaza]

@Jogai That sounds great. I'll take care of it!

I will start by auditing the list to identify archived repositories or those with no updates in more than 3 years to proceed with their removal. Regarding the Vue 2 resources, I'll follow your suggestion and prepare a draft to move them to a dedicated README-vue-2.md so the main list stays clean and focused on Vue 3.

I'll start with the UI Components section as it's one of the largest, and I'll submit a PR once I have the first set of cleanups ready.