.github/funding.yml

@@ -0,0 +1 @@
+open_collective: js-org

.github/workflows/validate.yml

@@ -0,0 +1,86 @@
+name: Validate
+
+on:
+  push:
+    branches:
+      - master
+  pull_request:
+    branches:
+      - master
+    types:
+      - opened
+      - reopened
+      - edited
+      - synchronize
+
+permissions:
+  contents: read
+
+jobs:
+  validate-cnames:
+    runs-on: ubuntu-latest
+
+    env:
+      GH_EVENT_HASH: ${{ github.event_name == 'pull_request' && github.event.pull_request.head.sha || github.sha }}
+
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          ref: ${{ env.GH_EVENT_HASH }}
+
+      - uses: actions/checkout@v4
+        with:
+          repository: js-org/js.org-cleanup
+          path: cleanup
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version-file: cleanup/.nvmrc
+          cache: npm
+          cache-dependency-path: cleanup/package-lock.json
+
+      - name: Install dependencies
+        run: npm ci
+        working-directory: cleanup
+
+      - name: Validate cnames_active.js
+        run: node index.js --validate ../cnames_active.js
+        working-directory: cleanup
+
+  validate-pr-template:
+    if: github.event_name == 'pull_request'
+
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Validate PR template
+        uses: actions/github-script@v7
+        with:
+          script: |
+            const body = context.payload.pull_request.body || "";
+
+            // 1. Check both checkboxes
+            const checkbox1 = /\[x\].*?There is reasonable content/i.test(body);
+            const checkbox2 = /\[x\].*?I have read and accepted/i.test(body);
+
+            // 2. URL must be on the exact "The site content can be seen at ..." line
+            // https://regex101.com/r/N36fsT
+            const urlLineRegex = /^[ \t]*-[ \t]*The site content can be seen at[ \t]+(?:<)?(?:\[.*?\]\()?https?:\/\/[^\s>()]+(?:\))?(?:>)?/m;
+            const urlMatch = urlLineRegex.exec(body);
+            const urlValid = urlMatch !== null;
+
+            // 3. Explanation must follow the blockquote marker
+            const explanationMatch = />\s*The site content is(?:\s*|\s*\n)(.+)/i.exec(body);
+            const explanation = explanationMatch && explanationMatch[1].trim().length > 10;
+
+            if (!checkbox1 || !checkbox2 || !urlValid || !explanation) {
+              core.setFailed(
+                "❌ PR template is not properly filled:\n" +
+                `Checkbox1: ${checkbox1 ? '✅' : '❌'}\n` +
+                `Checkbox2: ${checkbox2 ? '✅' : '❌'}\n` +
+                `URL on correct line: ${urlValid ? '✅' : '❌'}\n` +
+                `Explanation: ${explanation ? '✅' : '❌'}`
+              );
+            } else {
+              console.log("✅ PR template format is valid.");
+            }

.prettierrc.json

@@ -0,0 +1,16 @@
+{
+  "printWidth": 1000,
+  "quoteProps": "preserve",
+  "semi": false,
+  "singleQuote": false,
+  "tabWidth": 2,
+  "trailingComma": "none",
+  "overrides": [
+    {
+      "files": "records_restricted.js",
+      "options": {
+        "tabWidth": 4
+      }
+    }
+  ]
+}

PULL_REQUEST_TEMPLATE.md

@@ -1,2 +1,17 @@
-- [x] There is reasonable content on the page (see: [No Content](https://github.com/js-org/js.org/wiki/No-Content))
-- [x] I have read and accepted the [Terms and Conditions](http://js.org/terms.html)
+<!--
+
+Thanks for creating a pull request to request a new subdomain from JS.ORG
+
+Before creating your pull request, please complete the following steps:
+
+- Ensure that your pull request changes only the cnames_active.js file, adding a single new line for your subdomain request
+- Tick the two checkboxes, agreeing to the sentences, below by placing an x inside the square brackets ([ ] becomes [x])
+- Add a link (GitHub repository, Vercel deployment, etc.) and explanation below for your content so we can validate your request
+
+-->
+
+- [ ] There is reasonable content on the page (see: [No Content](https://github.com/js-org/js.org/wiki/No-Content))
+- [ ] I have read and accepted the [Terms and Conditions](http://js.org/terms.html)
+- The site content can be seen at <link>
+
+> The site content is ...

README.md

@@ -1,24 +1,70 @@
-[![JS.ORG Logo](http://logo.js.org/png/github_header.png)](http://js.org)
-
 [![JS.ORG](https://img.shields.io/badge/js.org-+-FFE70B.svg?style=flat-square)](http://js.org)
-[![PRs](https://img.shields.io/github/issues-pr-closed-raw/js-org/js.org.svg?style=flat-square&colorB=31a88b&label=Pull%20Requests)](https://github.com/js-org/js.org/pulls?q=is%3Apr+is%3Aclosed+label%3Aadd)
-[![Donate](https://img.shields.io/badge/Donate-for_registrar_fees-blue.svg?style=flat-square&logo=paypal)](https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=RPBWBDBKW62AC)
+[![PRs](https://img.shields.io/github/issues-pr-closed-raw/js-org/js.org.svg?style=flat-square&colorB=FFE70B&label=pull%20requests)](https://github.com/js-org/js.org/pulls?q=is%3Apr+is%3Aclosed+label%3Aadd)
+[![Contributors](https://img.shields.io/github/contributors-anon/js-org/js.org?color=FFE70B&style=flat-square)](https://github.com/js-org/js.org/graphs/contributors)
+[![Activity](https://img.shields.io/github/commit-activity/m/js-org/js.org?color=FFE70B&style=flat-square)](https://github.com/js-org/js.org/pulse/monthly)
+[![Donate](https://img.shields.io/badge/Donate-for_registrar_fees-1F87FF.svg?style=flat-square&logo=open-collective&logoColor=fff)](https://opencollective.com/js-org)
+
+---
 
-**To get a short and sleek subdomain for your own GitHub Pages site follow these 4 Steps:**
+## GitHub Pages
+
+To get a short and sleek subdomain for your own GitHub Pages site from JS.ORG follow these 4 steps:
 
 ### Step 1
-If you haven't already, now it's time to log in to your GitHub account and set up your GitHub Pages site following the instructions [here](https://pages.github.com/). To get a head start you can simply use the generator with one of the provided themes and **add some reasonable content to your new page**.
+
+If you haven't already, log in to your GitHub account and set up your GitHub Pages site following [their instructions](https://pages.github.com). **Make sure to add some reasonable content to your new page**.
 
 ### Step 2
-Now determine your js.org subdomain: either choose your username or the name of your repo according to the existing GitHub Pages URL (for ```http://foo.github.io/bar```, either ```foo.js.org``` or ```bar.js.org``` would be possible). More details in the [wiki](https://github.com/js-org/js.org/wiki).
+
+Now determine your JS.ORG subdomain: either choose your username or the name of your repository according to the existing GitHub Pages URL (for `http://foo.github.io/bar`, either `foo.js.org` or `bar.js.org` would be possible). We have more guidance on picking an appropriate subdomain in our wiki: <https://github.com/js-org/js.org/wiki/Subdomain-Determination>.
 
 ### Step 3
-Add a file named ```CNAME``` to your repo (in the ```gh-pages``` branch for project pages) with a single line matching the domain you have chosen (e.g. ```foo.js.org```). If you prefer a webinterface form, have a look at [GitHub Pages Help](https://help.github.com/articles/adding-or-removing-a-custom-domain-for-your-github-pages-site/).
+
+If you're [publishing from a branch](https://docs.github.com/en/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site#publishing-from-a-branch):
+
+Add a file named `CNAME` to your repo (in the `gh-pages` branch for project pages, or the branch that you've set as your GitHub Pages source) with a single line matching the domain you have chosen (e.g. `foo.js.org`). You can also use the UI in the repository settings as discussed below, if desired.
+
+If you're [publishing using a workflow](https://docs.github.com/en/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site#publishing-with-a-custom-github-actions-workflow):
+
+A `CNAME` file will not be processed when publishing a site via a workflow, so you will need to use the UI in the repository settings to [add the custom domain](https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain). Head into the repository settings and under the Pages tab add your JS.ORG subdomain as a custom domain.
 
 ### Step 4
-To finish the procedure, make a pull request in this GitHub repository that adds your subdomain to the [list](https://github.com/js-org/js.org/blob/master/cnames_active.js) of existing JS.ORG domains. Your new URL should go live within 24 hours (keep an eye on your pull request in case of a naming conflict).
-
-# 
 
-### Thanks
-... to **[Cloudflare](https://www.cloudflare.com)** for their superb DNS service that makes this possible. While JS.ORG is using their free plan - to a shameless extent - they helped us more than once with some flexible solutions and extended quotas. Many thanks!
+To finish the procedure, make a pull request in this GitHub repository that adds your subdomain to the [subdomains list](https://github.com/js-org/js.org/blob/master/cnames_active.js) of existing JS.ORG domains. Your new URL should go live within 24 hours (keep an eye on your pull request in case of a naming conflict or if there are requested changes).
+
+## Other Providers
+
+If you'd like to use JS.ORG for a website hosted elsewhere, you can do that too!
+
+### Step 1
+
+If you haven't already, get your site set up with whatever hosting provider you desire. Note that to use JS.ORG, your hosting provider will need to support adding custom domains via a CNAME DNS record.
+
+### Step 2
+
+Now determine your JS.ORG subdomain: either choose your username or the name of your repository according to the existing GitHub Pages URL (for `http://foo.github.io/bar`, either `foo.js.org` or `bar.js.org` would be possible). We have more guidance on picking an appropriate subdomain in our wiki: <https://github.com/js-org/js.org/wiki/Subdomain-Determination>.
+
+### Step 3
+
+Follow your hosting provider's instructions for adding a custom domain to your site, if configuration is needed. Our wiki contains a list of hosting providers we've seen folks successfully use in the past, including some notes on correctly configuring some of them: <https://github.com/js-org/js.org/wiki/3rd-party-hosts>.
+
+### Step 4
+
+As above with adding a subdomain to a GitHub Pages site, the final step is to make a pull request in this GitHub repository that adds your subdomain to the [subdomains list](https://github.com/js-org/js.org/blob/master/cnames_active.js) of existing JS.ORG domains.
+
+---
+
+> [!IMPORTANT]
+> Please be aware that there are some rules that apply to website content hosted on JS.ORG subdomains:
+>
+> **Websites must be *directly* related to the JavaScript ecosystem/community (such as NPM packages / JS tools, not personal pages / portfolios)**
+> 
+> - No placeholder pages. Websites must contain substantive content relevant to their purpose.
+> - No automatic redirects away from the **js.org** domain. Redirects must require user interaction.
+> - No unrelated content. Websites must stay focused on their intended topic or purpose.
+>
+> _Additionally, please be aware of our full [Terms and Conditions](https://js.org/terms.html) for the JS.ORG service._
+
+---
+
+Thanks to **[Cloudflare](https://www.cloudflare.com)** for their awesome DNS service that makes this service possible. While JS.ORG is using their free plan - to a shameless extent - they helped us more than once with some flexible solutions and extended quotas. Many thanks!