share

Client-facing pages for proposals and sales decks, hosted via GitHub Pages on https://share.yourbi.nl. One folder per client, each deck password-protected with StatiCrypt (AES-256, client-side).

How it works

• Every folder in this repo becomes a URL: symbro/index.html → https://share.yourbi.nl/symbro/
• Each index.html is a StatiCrypt-encrypted page: the visitor enters a password, the deck decrypts in the browser. Without the password the file is unreadable — including here in the repo.
• GitHub Pages deploys from the main branch automatically. A commit is live in about a minute (progress under the Actions tab).
• The root URL (share.yourbi.nl) intentionally returns a 404: there is no index in the root, so client folders cannot be browsed. Folder names are guessable, which is fine — the content is what’s protected.

Adding a new deck

1. Export the deck as a single self-contained HTML file (e.g. from Claude Design).
2. Encrypt it with StatiCrypt using the YourBI login template (light theme, logo, English copy, blue button). Easiest: hand the HTML to Claude and ask for an encrypted, upload-ready index.html — it generates a strong password as well.
3. Upload via Add file → Upload files on main. The file lands in the root as index.html.
4. Open the file → click the pencil (Edit) → prefix the filename with the client folder: clientname/index.html → Commit directly to main. GitHub creates the folder and moves the file.
5. Wait ~1 minute, then test https://share.yourbi.nl/clientname/ in an incognito window.
6. Store the password in the password manager under share.yourbi.nl/clientname.

Folder naming: lowercase, no spaces, client name only (symbro, axivate, vermaat).

Sharing with a client

• Send the link and the password through different channels (e.g. link by email, password by WhatsApp/Signal/phone).
• One password per client/deck. Never reuse passwords across clients.
• Passwords live in the password manager only — never in this repo, never in the same email as the link.

Replacing or removing a deck

• Update: encrypt the new version (a new password is fine; update the password manager) and overwrite clientname/index.html.
• Revoke access: delete the folder and commit. The URL 404s within a minute. Note that anyone who had the password could have saved the page while it was live — treat published decks as shared.

Technical notes

• Custom domain: share.yourbi.nl, configured via a CNAME record pointing to your-bi.github.io and the CNAME file in the repo root. Do not delete or edit that file.
• Enforce HTTPS is enabled in Settings → Pages. Keep it on: the password is submitted in the browser, so pages must only be served over HTTPS.
• Pages publishing for this org is enabled under Organization → Settings → Member privileges → Pages creation (public). The enterprise level has no restricting policy.
• Repo visibility is Internal: everyone in the YourBI enterprise can see this repo, including encrypted decks (unreadable without password) and this README.
• Size limits: GitHub Pages caps published sites at 1 GB and ~100 GB bandwidth/month — no practical constraint for decks of ~1 MB each.