No Content

Before JS.ORG can accept a pull request there has to be "reasonable content" on the page (as stated in step 1 of the readme!). There has to be at least an index.html with some texts, links, images,... You should give anybody a clear picture what your page is (or will be) about.

This rule exists to avoid name grabbing where people reserve one or more subdomains for later use but never put any content on the page. JS.ORG doesn't support this misbehaviour. And of course we also want to focus entirely on JavaScript.

Two examples to explain this further:

• https://github.com/caracal7/fun.js is considered "no content" and gets rejected (see #125)
• https://finder.js.org is ("not-very-shiny and probably already outdated but valid") content that gets accepted (see #15)

more examples with label "no content"

Also of note is that you cannot have a JS.ORG subdomain that simply redirects the user to somewhere outside of JS.ORG (automatic redirects to other JS.ORG subdomains are permitted). If you do need to send the user somewhere else, this must be via a manual user interaction (a button or a link), not anything automatic.

Two examples to explain this further:

• https://node.js.org
• https://next.js.org