feat: add Eleventy landing page with GitHub Pages deployment

Author: alexcmgit

.github/workflows/deploy.yml

@@ -0,0 +1,38 @@
+name: Deploy Eleventy to GitHub Pages
+on:
+  push:
+    branches: [main]
+  workflow_dispatch:
+permissions:
+  contents: read
+concurrency:
+  group: pages
+  cancel-in-progress: false
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 22
+          cache: npm
+      - run: npm ci
+      - run: npm run build
+      - uses: actions/configure-pages@v5
+      - uses: actions/upload-pages-artifact@v3
+        with:
+          path: _site
+  deploy:
+    needs: build
+    runs-on: ubuntu-latest
+    permissions:
+      pages: write
+      id-token: write
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    steps:
+      - name: Deploy
+        id: deployment
+        uses: actions/deploy-pages@v4

.gitignore

@@ -0,0 +1,4 @@
+node_modules/
+_site/
+.DS_Store
+.local/

.tool-versions

@@ -0,0 +1 @@
+nodejs 22.23.3

README.md

@@ -0,0 +1,52 @@
+# libsrc.dev
+
+A small Eleventy landing page for the libsrc GitHub organization. Static HTML and CSS, with no browser JavaScript or external fonts. Project content lives in `src/_data/site.json`.
+
+## Local development
+
+Install Node.js 22 or newer, then run:
+
+```sh
+npm ci
+npm run dev
+```
+
+Open the localhost URL printed by Eleventy. `npm run build` generates the deployable site in `_site/`.
+
+### Typography
+
+The local preview uses TT Firs Neue Regular and Medium from the supplied trial archive. These files live in ignored `.local/fonts/` and are copied only in Eleventy's serve mode. The included TypeType trial license permits evaluation but restricts public webpages. Production builds clean `_site/` first to prevent preview fonts from being deployed, and use the system sans-serif fallback. For public TT Firs Neue use, replace the trial with licensed webfont files and enable their font-face rules in the production stylesheet.
+
+The online dependency audit currently reports advisories in Eleventy's development dependencies, with no suitable stable upgrade offered. The deployed output contains only static files; keep the development server local and use trusted build inputs.
+
+## Deploy to GitHub Pages
+
+1. Push this project to an organization repository, preferably `libsrcdev/libsrcdev.github.io`, on the `main` branch.
+2. In repository **Settings → Pages**, set the source to **GitHub Actions**. Run the included deployment workflow if it hasn't run yet.
+3. Set the Pages **Custom domain** to `libsrc.dev` and save it before changing DNS. An Actions deployment uses this setting; a `CNAME` file is not required.
+4. At your DNS provider, point the apex (`@`) to GitHub Pages using these four A records:
+
+   | Type | Name | Value |
+   | --- | --- | --- |
+   | A | @ | 185.199.108.153 |
+   | A | @ | 185.199.109.153 |
+   | A | @ | 185.199.110.153 |
+   | A | @ | 185.199.111.153 |
+
+   Replace conflicting website A/AAAA records; preserve mail and TXT records. Alternatively, use an ALIAS/ANAME to `libsrcdev.github.io` if your provider supports it. Optional `www`: CNAME to `libsrcdev.github.io`.
+5. Once GitHub provisions the certificate, enable **Enforce HTTPS**. DNS and certificate provisioning can take up to 24 hours.
+6. Add the domain verification TXT record supplied by the service requiring verification. Use its exact host/name and value, not a placeholder. This is separate from any GitHub domain verification TXT record.
+
+Official reference: [GitHub Pages custom domain setup](https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site).
+
+## Verify the eligible domain
+
+```sh
+curl --head https://libsrc.dev/
+dig libsrc.dev A +short
+dig libsrc.dev TXT +short
+```
+
+The HTTPS HEAD request must return **HTTP 200 directly**, without requiring a redirect, login, or challenge. Do not use `curl -L` when checking this requirement. Query the specific TXT hostname supplied by the verification service if it is not the apex.
+
+`libsrc.dev` is an apex domain. Eleventy generates its homepage, but the hosting provider serves HTTP requests and TLS; a local build alone does not prove domain eligibility. Deployment, DNS access, the issued certificate, and the live HEAD response must all be verified before submitting the domain.

eleventy.config.js

@@ -0,0 +1,10 @@
+export default function (eleventyConfig) {
+  const previewFonts = process.env.ELEVENTY_RUN_MODE === "serve";
+  eleventyConfig.addGlobalData("previewFonts", () => process.env.ELEVENTY_RUN_MODE === "serve");
+  if (previewFonts) {
+    eleventyConfig.addPassthroughCopy({ ".local/fonts": "assets/fonts" });
+  }
+  eleventyConfig.addPassthroughCopy("src/assets");
+  eleventyConfig.addPassthroughCopy("src/robots.txt");
+  return { dir: { input: "src", output: "_site" } };
+}