Incubate

[sindresorhus]

If you just starting working on a list, you can post it here to indicate that you are working on it (prevents duplicates) and to gather feedback.

One comment per list draft. Open an issue on the list to provide feedback. Not here.

[nuzulul]

started awesome-webrtc

[dreikanter]

Started awesome-vst.

[wongyah]

Started awesome-technical-writing-learning

[hlaueriksson]

Preparing awesome-powertoys-run-plugins

[hbrns]

Started awesome-tana

[michaelachrisco]

Started https://github.com/michaelachrisco/awesome-edi based on https://github.com/michaelachrisco/Electronic-Interchange-Github-Resources

[hstsethi]

Working on awesomeizing https://github.com/hstsethi/awesome-j2me

This is a list about Mobile Information Device Profile(MIDP), a Java ME specification designed for old keypad phones and PDAs. MIDP is used to create Midlets, which have .jad or .jar extension, and run on platforms like old keypad phones or PDAs.

Finished adding TOC, using "-", added awesome icon, changed repo name and some other stuff.

[Lissy93]

No longer considering Lissy93/awesome-privacy for here

As I couldn't continue with "Non-generated Markdown file in a GitHub repo." ^[L63] criteria, as it meant I had to duplicate things in order to maintain awesome-privacy.xyz.

I'm interested to hear if / how anyone else manages an interactive site for their awesome list, while keeping content in pure markdown format? 🤔

[slevithan]

Recently started awesome-regex, but it's well underway.

[ChrisCarini]

No longer considering Lissy93/awesome-privacy for here

As I couldn't continue with "Non-generated Markdown file in a GitHub repo." [L63] criteria, as it meant I had to duplicate things in order to maintain awesome-privacy.xyz.

I'm interested to hear if / how anyone else manages an interactive site for their awesome list, while keeping content in pure markdown format? 🤔

Hi @Lissy93 !!! 👋 - I don't have a suggestion here, however I initially had a similar desire in https://github.com/matchai/awesome-pinned-gists/issues/54#issuecomment-1367489734 (an "awesome" repo I assist in maintaining) to be able to add standardization/structuring (and, lint-ing and validations for PRs, etc). I'd personally love to see this requirement opened up a bit to help maintainers automate easier.

I'd love to hear if other maintainers of awesome-list repos are encountering a similar problem/desire here.

[secondtruth]

There's an awesome-list I'm working on (awesome-webtech) for the Open WebTech Association – a community I'm currently working on to bring developers of innovative web-based projects together, share knowledge, and eventually develop open standards. The document is listing various projects like communication systems, advanced webtops, devops tools, P2P services, and AI platforms, being open source, with an inclusive community, and following other guidelines.

[Polycarbohydrate]

Hello! Started working on awesome-tor.

Awesome Tor is a curated list of resources, tools, and applications related to the Tor network.

Wish me luck! Edit: Finished Application and Bridges section. Added contributing.md along with code of conduct.

[szdytom]

Started Awesome Practical C++.

A filtered list of the most practical and recognized C++ frameworks and libraries that are production ready.

[szdytom]

No longer considering Lissy93/awesome-privacy for here

As I couldn't continue with "Non-generated Markdown file in a GitHub repo." [L63] criteria, as it meant I had to duplicate things in order to maintain awesome-privacy.xyz.

I'm interested to hear if / how anyone else manages an interactive site for their awesome list, while keeping content in pure markdown format? 🤔

Hi @Lissy93 !!! 👋 - I don't have a suggestion here, however I initially had a similar desire in https://github.com/matchai/awesome-pinned-gists/issues/54#issuecomment-1367489734 (an "awesome" repo I assist in maintaining) to be able to add standardization/structuring (and, lint-ing and validations for PRs, etc). I'd personally love to see this requirement opened up a bit to help maintainers automate easier.

I'd love to hear if other maintainers of awesome-list repos are encountering a similar problem/desire here.

Hi @Lissy93 @ChrisCarini I've just started https://github.com/szdytom/awesome-practical-cpp and I have the same problem. I wrote a program to create the list because I dont't want to copy-and-paste the badge links again and again.

Another interesting fact is that some awesome list created long ago don't or no longer fellows the criteria. I guess your list won't be removed if you start automation after your list is accepted.

[Bricenode]

Great

[emmanuelgautier]

Started a list about Zanzibar resources: https://github.com/cerberauth/awesome-zanzibar

Not a lot of resources (yet)

[davidmytton]

Started Awesome Frontend Security.

[StanimirIglev]

Started Awesome XML

[Preacher27]

Thank you your the first person to tell me this

[0xAnalyst]

Built this for email security https://github.com/0xAnalyst/awesome-email-security . did follow the guideline but I welcome any feedback on that or contributions before I submit the pull request

[tyaga001]

Started awesome-neondb