docs: add new organisation readme

[souravjain540]

adding new organisation readme.

[netmilk]

Thank you, @souravjain540!

The only two things that come to my mind are:

• Crawlee py + js lines have a significantr repetition. What about squishing them into one line to align with the umbrella Crawlee page strategy and refer to "Crawlee for JavaScript" and "Crawlee for Python"? We could save some vertical space.

  For example:
  Crawlee: A web scraping and browser automation library for Node.js and Python to build reliable scrapers.

• I'd consider mentionioning Actor Creation (authoring) in the Learn section more specifically. That's what we want to stress in the communication to the developer persona the most.

But it looks awesome otherwise and I'm leaving all that up to your consideration. :)

[souravjain540]

done @netmilk!

[netmilk]

Suggested change

	<li>Find hundreds of ready-made Actors for your web scraping or automation project. Or create and <a href="https://apify.com/store/">publish your own.</a> 💻</li>
	<li>Find hundreds of ready-made Actors for your web scraping or automation project. Or <a href="https://docs.apify.com/platform/actors/development/quick-start/locally">create</a> and <a href="https://apify.com/store/">publish your own.</a> 💻</li>

[jancurn]

Thanks for that. Few small comments: please let's add proxy chain, it's one of our most popular repos.

The hyperlinks contain also ":" (e.g. fingerprint-suite: ), pls let's format it correctly.

[jancurn]

Also "monetize your dev skills through Apify Docs" doesn't make much sense, each bullet point should communicate one thing: find ready-made Actors, learn web scraping, build your Actors, publish & monetize them, learn more

[souravjain540]

@jancurn done with changes, let me know if it is okay to merge now :)

[jancurn]

Cool, go for it