A living digital shrine to the Khyapa Parampara tradition
Dedicated to Gurushreshta Ma Adya Mahakali and Baba Kalabhairava
This repository is the complete source code for jaikhyapaparampara.com — a spiritual knowledge archive preserving the oral wisdom of the Khyapa Parampara lineage.
The site contains 1,204 articles: word-for-word conversations, Guru stories, spiritual discourses, and prophecies — originally spoken in Bengali, transcribed from YouTube and translated into English.
The Khyapa Parampara is a living Tantric lineage rooted in the worship of Ma Kali and Kalabhairava Baba. Its teachings are available now in English. Khyapas — mean the divine mad who dont shy away from the truth. Irrespective of the consequences.
This site documents two luminaries of the lineage:
| Teacher | Role |
|---|---|
| Gurubaba Shyama Khyapa | ChaturthaPurusha — the fourth realized master of the Khyapa Parampara; GuptaSadhaka (hidden practitioner) |
| Shri Praveen RadhaKrishnan | Founder of the Kaliputra Mission; and my Guru ❤️ |
Compiled with devotion by KaliPutra-Ashish. Curated for all seekers.
The site also hosts free downloadable ebooks:
- Adya Mahakali Sahasranama — 1000 names with chanting guide (English & Hindi)
- Kalabhairava Sahasranama — 1000 names with chanting guide (English & Hindi)
- Kalabhairava Ashtottara Namavali — 108 names with chanting guide (English)
| Layer | Technology |
|---|---|
| Static site generator | Eleventy (11ty) v2 |
| Templating engine | Liquid (Eleventy built-in) |
| Content format | Markdown + YAML frontmatter + inline HTML |
| Deployment | Cloudflare Pages (auto-deploy on push to main) |
| Node version | 18 (pinned in .node-version) |
# Clone the repository
git clone https://github.com/09ashishkapoor/jaikhyapaparampara.git
cd jaikhyapaparampara
# Install dependencies
npm install
# Build to _site/
npm run build
# Serve locally with live reload at http://localhost:8080
npm startAfter cloning, the site builds and serves identically to production — no environment variables or secrets required.
This repo now ships with a lightweight Playwright-based validation baseline for merge review:
- smoke coverage for the homepage, search flow, and sacred art gallery
- a scoped
@axe-core/playwrightaccessibility check for the search experience - 3 stable visual regression snapshots
- a homepage performance budget test
- GitHub Actions for Playwright validation and CI link checking
All validations run automatically before every git push (including VS Code sync). If any test fails, the push is blocked until fixed — no manual steps needed.
Note: The performance budget test is excluded from the pre-push hook — LCP timing varies by machine and runs reliably on GitHub CI only. All other tests (smoke, accessibility, visual snapshots) run locally.
To bypass in an emergency:
git push --no-verify# Install browser dependencies once after npm install
npx playwright install chromium
# Run the full validation suite manually
npm run validatenpm run validate:update-snapshotsRe-run npm run validate after refreshing snapshots, then review the changed files under tests/visual/*-snapshots/ before committing.
For the repo-standardized pattern and reuse notes, see VALIDATION_BASELINE.md.
articles/ # 1204 Markdown articles
_includes/ # Liquid templates
│ base.liquid # Site shell (head, nav, footer)
│ article.liquid # Per-article layout
images/ # Site images (WebP optimised)
markdownfiles_forblog/ # Raw YouTube transcript staging area
│ tobeprocessed/ # Awaiting conversion → articles/
│ processed/ # Converted transcripts (archive)
│ redundant/ # Duplicates / retired files
docs/ # How-to guides and editorial notes
scripts/ # Python build & audit helpers
.eleventy.js # Eleventy build config
wrangler.toml # Cloudflare Pages config
styles.css / styles.min.css # Stylesheet (source + minified)
script.js / script.min.js # Frontend JS (source + minified)
sitemap.liquid # Sitemap template → sitemap.xml
search-index.11ty.js # Client-side search index (JS template)
gallery.html # Sacred image gallery
_headers # Cloudflare HTTP response headers
_redirects # Cloudflare URL redirects
Every article in articles/ is a Markdown file with YAML frontmatter followed by an HTML transcript body.
layout: article
title: "Full Title Here"
breadcrumbTitle: "Short 5-7 Word Version"
description: "1-2 sentence summary."
keywords: "Guru Deva Shyama Khyapa, Gupta Sadhak, Smashana Bhairava, Khyapa Parampara, [topic terms]"
category: "Guru Stories" # or "Spiritual Teachings" or "Discourse"
author: "🗣️ Gupta Sadhak Shyama Khyapa"
date: 2026-03-05
readingTime: 6 # ceil(wordCount / 200)
tags:
- articles
- Guru Baba Shyama Khyapa
- [topic-specific tags]
source: |
<p><strong>Source:</strong> YouTube video | Bengali to English Translation</p>
<p><a href="https://www.youtube.com/watch?v=VIDEO_ID" target="_blank" rel="noopener">📺 Watch Original Bengali Video</a></p>
<p style="margin-top:0.5rem;"><em>Verified by Kaliputra-Ashish</em></p>Dialogue is structured in transcript-container / speaker-block HTML — not plain Markdown paragraphs:
<div class="transcript-container" style="background:rgba(45,15,24,0.4);border:1px solid var(--border-gold);padding:2.5rem;border-radius:8px;box-shadow:0 10px 30px rgba(0,0,0,0.3);margin-bottom:2rem;">
<div class="speaker-block" style="margin-bottom:2rem;border-left:3px solid var(--accent-color);padding-left:1.5rem;">
<span class="speaker-name" style="font-weight:700;color:var(--accent-bright);margin-right:0.5rem;text-transform:uppercase;letter-spacing:1px;font-size:1rem;">GURU SHYAMA KHYAPA:</span>
<span class="speech-text" style="display:block;margin-top:0.5rem;">The full text of what was said.</span>
</div>
</div>Common speaker labels: DEVOTEE:, GURU SHYAMA KHYAPA:, NARRATOR:.
Contributions of any kind are welcome — corrections, new transcript conversions, translations, or code improvements.
- Fork the repository and create a branch.
- Add or edit your article in
articles/following the frontmatter schema above. - Run
npm run serveand preview locally. - Open a pull request with commit message format:
content: add article - <short-title>
Cloudflare Pages auto-deploys on every push to main. The build output directory is _site/ (configured in wrangler.toml). No extra secrets or environment variables are needed.
To deploy your own fork:
- Connect the repository to Cloudflare Pages.
- Set build command:
npm run build - Set output directory:
_site
After editing styles.css or script.js, regenerate the minified versions:
python minify-css.py
python minify-js.pyThe code is MIT. The teachings belong to the tradition. Share freely.
MIT — use it, copy it, build on it. See LICENSE for the full text.