vapor-community / awesome-vapor Goto Github PK

README.md

I updated all those packages that already support 4.0. I also deleted the two dead vapor services and the dead VaporNation newsletter.

I also request information on whether packages were still under development from a number of people and will update as I hear.

Seeing as the list is nicely growing both in terms of entries and in terms of popularity¹ (thank you! 🙇 ✨), I think it’s time to start thinking about splitting the list of Vapor libraries into relevant categories. And since I’m notoriously bad at making creative decisions like these myself, I’d love to invite the community to participate in the process of decision-making.

In your opinion, what sort of categories would reasonably separate the libraries currently present on the list, and hopefully not require too many changes in the future?

From my point of view, the ideal situation would look like this:

• categories are distinct enough that each library can without any reasonable doubt belong to one category only;
• categories are intuitive enough that if I’m searching for a solution of a particular problem, I should immediately know which category will likely contain libraries solving my problem just by looking at the category list in the table of contents;
• categories are generic enough to describe not only current state of the list, but hopefully also future state.

I’d love to hear what other people think and in a week or two’s time, make a final decision based on the feedback I receive by then (if any).

This is the Guardian's address:

https://github.com/Jinxiansen/Guardian

Thank you! ☺️

Would you consider replacing Vapor2/Vapor3's icons with their alt text (v2/v3) ? Images aren't searchable 😞

Awesome guidelines
Awesome manifesto

What do you think about starting to add links to content about Vapor 4? I saw that there are a couple of articles popping up about the beta.

Hey,

I'm just wondering why Vapor2 is a requirement in PULL_REQUEST_TEMPLATE.md? 🙂