Clarivo Research & Evidence — GitHub Pages website

This is the production, multi-page static website for Clarivo Research & Evidence: Clear evidence. Better decisions. It uses semantic HTML, modern CSS and vanilla JavaScript. There is no build step, database, framework or paid runtime.

What is included

• 16 HTML pages, including services, research, publications, methods, ethics, about, contact, payments, privacy, terms, accessibility, image credits, two original notes and a 404 page.
• Responsive light and dark themes.
• Accessible mobile navigation, visible keyboard focus, reduced-motion support and essential no-JavaScript fallbacks.
• Editable publication library and site configuration.
• Real, licensed photographs with a complete credits page.
• GitHub Actions workflow for Pages deployment.
• Sitemap, robots file, manifest, favicon, social card and structured data.
• No analytics, advertising tracker, external font or client-side secret.

The two files you edit most often

1. assets/js/site-config.js — domain, public email, location and payment availability.
2. assets/js/library-data.js — public projects, publications and insights. Keep published: false until a record is verified and approved for release.

The site currently uses the working URL https://clarivoresearch.tech and the working email contact@clarivoresearch.tech. Replace them before public launch if they are not verified.

Configure the public URL and email in one command

Node.js 18 or newer is sufficient. From the website folder, run:

node tools/configure-site.mjs https://YOUR-PUBLIC-URL YOUR-VERIFIED-EMAIL

Examples:

node tools/configure-site.mjs https://clarivoresearch.tech contact@clarivoresearch.tech

node tools/configure-site.mjs https://YOUR-ACCOUNT.github.io/clarivo-research-evidence contact@example.org

The second example is for a GitHub project site. Keep the repository name in the URL.

Fastest deployment tonight: project repository

1. Create a new public GitHub repository, for example clarivo-research-evidence.
2. Run the configuration command using the final GitHub Pages URL and a verified email address.
3. Upload the contents of this folder to the repository root—not an extra enclosing folder.
4. Commit to the main branch.
5. Open the repository’s Settings → Pages.
6. Under Build and deployment, choose GitHub Actions as the source.
7. Open the Actions tab and wait for “Deploy Clarivo to GitHub Pages” to complete.
8. Open the URL shown in the successful deployment and test navigation, theme, contact email and mobile layout.

The workflow is in .github/workflows/deploy-pages.yml.

Account or organisation site

For the root URL https://ACCOUNT.github.io/, the repository must normally be named ACCOUNT.github.io. Upload this site to that repository and configure the base URL without a repository subpath.

If Clarivo should not expose a personal GitHub account name, create or use a Clarivo organisation account or add a verified custom domain.

Custom domain

1. Purchase and verify the domain before advertising it.
2. In GitHub, verify the custom domain for the account or organisation.
3. Open Settings → Pages, add the custom domain and save it before changing DNS.
4. Configure the required DNS records with the domain provider.
5. Copy CNAME.example to CNAME and replace its content only if your selected publishing method requires it. GitHub Actions custom-domain behaviour should be checked in the current GitHub documentation.
6. Run tools/configure-site.mjs using the final HTTPS domain.
7. Recommit the changed files and wait for deployment.
8. Enable Enforce HTTPS after GitHub confirms the certificate.

GitHub recommends verifying the domain to reduce takeover risk and recommends configuring www together with an apex domain. DNS and certificate changes can take time.

Contact form

The form does not send data to a server. It validates the fields and opens a prepared email in the visitor’s email application. This is honest and safe for a first static launch, but it depends on a configured email application.

Before connecting Formspree, Basin, Netlify Forms, Google Forms or another service, review:

• its privacy and international-transfer terms;
• spam protection and accessibility;
• retention and deletion controls;
• which staff can access submissions;
• whether it is suitable for the information requested.

Never permit confidential or identifiable research data to be uploaded through the public form.

Payments

The payment page deliberately does not publish mobile-money numbers, merchant codes, bank accounts or QR codes. It explains an invoice-first process. Add verified MTN MoMoPay, Airtel Money Pay, bank or international details only to approved invoices.

Photographs

All photographs are externally hosted and credited on image-credits.html and docs/IMAGE_SOURCES.md. For the most reliable production setup, download the authorised sizes through each source’s official interface, preserve licence records, optimise the files and change the page URLs to local assets/images/ paths.

Pre-launch documents

• docs/PRE_LAUNCH_CHECKLIST.md
• docs/IMAGE_SOURCES.md
• docs/QA_REPORT.md
• SECURITY.md

Brand and honesty controls

Do not add unverified years in business, project counts, client logos, staff names, testimonials, physical offices, registration numbers, partnerships or accreditations. A polished site can look mature without inventing history.

Clarivo must not present itself as a laboratory, clinical research organisation, ethics authority, regulator, journal or dissertation-ghostwriting service.