I bought js.org and want to “give it back” to the JavaScript community
What do you think would be most useful for the JS-community? Free subdomains for open-source projects? A CDN ? Community tools like blogs, forums, chats? *@js.org email adresses for "everyone"?
24 comments
[ 3.6 ms ] story [ 52.8 ms ] threade.g. https://js.org/express 301 redirects to https://www.npmjs.com/package/express
Another idea is a blog. One of my favorite blogs is http://npmawesome.com/
- When a project reaches a popularity threshold (for example 10k github stars or gets to be the most popular project is his category - example: the most popular 3D library) would get a subdomain:
https://jquery.js.org/eachplugin
https://node.js.org/express
When we get exceptions, in this case, express grew and got autonomous, https://node.js.org/express would redirect to:
https://express.js.org/
So you are safe, and can see if it at least work it out.
http://planet.lisp.org/
http://planet.emacsen.org/
http://www.planetnetbeans.org/
http://planetopendata.herokuapp.com/opendatanews?style=hacke...
There are probably several packages which will ease the creation of such a thing, but this is the one I know of: http://www.planetplanet.org/
For "javascript", I get w3schools.com/js !!! I know that Javascript is in constant evolution, but we need some kind of "headquarters to gather our troops", do PR and marketing.
JS community cannot be a Peter Pan forever, one day we must grow up.
[1] http://www.webplatform.org/
Also you could link/redirect references, like the Mozilla one https://developer.mozilla.org/en-US/docs/Web/JavaScript (Mozilla rocks \o/)
An initial Google search indicates there is a site like this for JavaScript, but checking it show it is an internet lifetime ago (5-6 years).
A fact based inventory of major JS libraries with downloads, bugs and updated_at stats would be helpful. The challenge would be keeping it fresh. If project "owners" can submit their own info that would help.
[1] https://www.ruby-toolbox.com/
Do not hustle with email, install a system to handle MX records by the user, maybe with an interface that has some defaults (github, gmail).
After that create an OAUTH provider. Now you can provide other services through partnerships. I would not give away the ability to define custom sub-subdomains, instead let them choose between different service providers for predefined subdomains like these:
* forum.project.js.org
* news.project.js.org
* issues.project.js.org
* mailinglist.project.js.org
Create a skin-able overview of all the services at project.js.org. For the beginning you could simply pull in githubs README and add a navigation bar at the top. Later you could create something more dynamic.
Host an aggregator for each service at:
* js.org/forum
* js.org/news
* js.org/issues
* js.org/mailinglist
After you successfully created an enormous community and locked everybody in, turn evil, go into profit mode and add:
* jobs.project.js.org
* donate.project.js.org
* sponsors.project.js.org