BMITDEE

Repository publication guide

Publish the BMITDEE JavaScript platform to GitHub

The complete repository ZIP is ready. These steps keep production secrets out, enable tests and Pages, and connect the public developer hub after the repository exists.

repository
bmitdee-js/
├── packages/core
├── packages/adaptive
├── packages/elements
├── packages/cli
├── test-vectors
├── methodology
├── examples
└── .github/workflows

Create the repository

Create a public repository named bmitdee-js under the GitHub account or organization you control. Do not initialize it with another README if you will upload this prepared repository.

Extract and inspect locally

Confirm the ZIP contains packages, tests, methodology, examples and workflows—and contains no config/db.php, credentials, user data or server logs.

Initialize and push

git init
git add .
git commit -m "Initial BMITDEE JS platform release"
git branch -M main
git remote add origin YOUR_REPOSITORY_URL
git push -u origin main

Enable GitHub Pages

In repository Settings → Pages, choose GitHub Actions. The included workflow validates the project and deploys the playground app.

Review Actions permissions

The workflows use read-only contents permission for tests and Pages-specific permissions for deployment. The release workflow writes release assets only when a version tag is pushed.

Create the first release

git tag v0.1.0
git push origin v0.1.0

The included release workflow creates a downloadable source asset and release notes.

Connect bmitdee.com

Edit /developers/config.js on the production site and set repositoryUrl and githubPagesUrl. The hidden “View on GitHub” controls will then appear without changing every page.

Pre-publication security checklist

  • No production database or mail configuration.
  • No AdSense account credentials beyond the public production ads.txt file—which is not part of this code repository.
  • No user measurements, emails, private history, tokens or analytics rows.
  • No journalist contact records or outreach lists.
  • Tests pass with npm run check.
  • TypeScript checks pass with npm run typecheck.
  • Repository visibility and issue-contact details are intentional.
Important: the website production ZIP and GitHub repository ZIP are separate. Upload the production-safe website package to cPanel; publish the dedicated bmitdee-js ZIP to GitHub.