You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TLTR: Just because something is created with JS doesn't mean it qualifies for a JS.ORG subdomain. Think of an arbitrary website - chances are high that more or less JS is involved. But that doesn't mean that every website qualifies for a JS.ORG domain....
If the JS code is mostly hidden from the visitor and is just part of the product, then it is more likely that it doesn't qualify for a JS.ORG domain.
In sharp contrast, there may be cases where there is no JS involved at all and a site still effortlessly qualifies for a JS.ORG subdomain. An example would be a site for a local JS meetup that is built and managed with a static site generator.
The goal is just to put more focus on JS when handing out subdomains...
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
See: #5496 and #5698 for more context.
TLTR: Just because something is created with JS doesn't mean it qualifies for a JS.ORG subdomain. Think of an arbitrary website - chances are high that more or less JS is involved. But that doesn't mean that every website qualifies for a JS.ORG domain....
If the JS code is mostly hidden from the visitor and is just part of the product, then it is more likely that it doesn't qualify for a JS.ORG domain.
In sharp contrast, there may be cases where there is no JS involved at all and a site still effortlessly qualifies for a JS.ORG subdomain. An example would be a site for a local JS meetup that is built and managed with a static site generator.
The goal is just to put more focus on JS when handing out subdomains...
Beta Was this translation helpful? Give feedback.
All reactions