Indexed by TopGit from live GitHub metadata: BabylonJS/Website has 217 stars, written primarily in JavaScript. Main babylon.js website
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
This website is built with Eleventy (11ty) using Nunjucks templates. All pages are configuration-driven — there are no individual .njk files per page. Instead, a single pagination template (src/pages.njk) generates every page from JSON config files.
How It Works
src/content/site.json defines the navigation menu, footer, social links, and global variables.
src/_data/pages.js reads the menu structure and resolves a config.json from each content directory.
src/pages.njk uses Eleventy pagination to generate one HTML page per entry.
Each config.json contains a blocks array. Each block specifies a templateName and content:
Per-page assets are discovered automatically by parsing the menu structure in site.json.
Installation
npm install
Development
Starts a local dev server at http://localhost:8080/ with live reload:
npm start
Production Build
npm run build
Output is written to the build/ directory.
Adding or Editing Pages
Create a directory under src/content/ with a config.json containing a blocks array.
Add a menu entry in src/content/site.json with a root matching the directory name.
The page is generated automatically on the next build.
To edit an existing page, modify its config.json — add, remove, or reorder blocks. Available block types are the .njk files in src/_includes/blocks/.
Pages use base.njk by default. A config can specify a layout from src/_includes/ for a different HTML scaffold. The /lite-partners/ showcase uses litePartners.njk to match the standalone Lite Demos gallery, with application cards defined in src/content/lite-partners/config.json. Its hidden menu entry registers the page and its assets without adding it to the main navigation.
Template Filters
{{ key | var }} — Resolves a value from site.json's variables object.
{{ obj | json }} — JSON-stringifies a value.
Updating the Website
This repository uses GitHub Copilot skills (.github/skills/) and helper scripts to automate content updates across the site. The blog post at .github/blog_post/BlogPost.md is the single source of truth for all feature content — every skill reads from it. See .github/INSTRUCTIONS.md for detailed workflow documentation.
Prerequisites
Before running any update, make sure the blog post is in place:
Save the release blog post markdown to .github/blog_post/BlogPost.md.
For homepage updates, save feature images to .github/raw_images/ and run npm run process-images.
What You Can Update with Copilot
Page
What to say
What happens
Homepage
"Update the homepage with new features"
Creates imageAndTextBlock entries in src/content/config.json with images, colors, descriptions, and links from the blog post.
Specifications
"Update the specifications page from the blog post"
Adds feature names and doc links to the ENGINE SPECIFICATIONS sections in src/content/specifications/config.json. Detects duplicates and checks column balance.
Feature Demos
"Add blog post demos to feature demos"
Adds demo entries to the gallery in src/content/featureDemos/config.json. Uses a two-pass workflow (see below).
Alt Text
"Add alt tags to the feature demos page"
Generates descriptive alt text for any config JSON file with image references. Works on any page.
How to Invoke a Skill
Open GitHub Copilot Chat and type a natural language prompt. You don't need to reference skill files — Copilot matches your request to the right skill automatically. Examples:
"Update the specifications page with the new features from the blog post"
"Add the new demos to the feature demos page"
"Add alt tags to the main page"
"Update alt text on the community page"
Each skill will read the blog post, compare against existing content, and present a plan before making changes. You confirm before anything is written.
Homepage Updates
The homepage skill handles the most complex update — converting blog post features into visual content blocks with images, background colors, descriptions, and links.
Process:
Place feature images in .github/raw_images/ (named to match the blog post image references).
Run npm run process-images to resize, optimize, and sample background colors. Colors are written to .github/image-colors.json.
Ask Copilot: "Update the homepage with new features from the blog post."
The skill creates imageAndTextBlock entries with alternating alignment, sampled background colors, condensed descriptions, and doc links.
Run npm start to preview at http://localhost:8080.
To update a single image later:
Place the updated image in .github/raw_images/ with an _updated suffix (e.g., particleFMAT_updated.png).
Run npm run update-image -- particleFMAT.
Update the background hex color in src/content/config.json with the value printed by the script.
Specifications Updates
Ask Copilot: "Update the specifications page from the blog post."
The skill extracts feature names and documentation links, then places each feature in the best-matching section (Main Features, Shaders/Rendering, Geometry, Optimizations, Special FX, Cameras, or Exporters and Tooling). It flags potential duplicates with existing entries and asks how to handle them. After adding all features, it checks whether the left and right columns are balanced and suggests moving whole sections if needed.
Feature Demos Updates (Two-Pass Workflow)
Automated screenshot capture of WebGL Playground demos is extremely resource-intensive (headless Chromium rendering full 3D scenes). Instead, the feature demos skill uses a manual screenshot workflow:
Pass 1 — Create entries with placeholders:
Ask Copilot: "Add blog post demos to feature demos."
The skill identifies non-Playground demo links (e.g., the Babylon.js Editor or Viewer Configurator) and asks whether to skip them.
It creates all config entries with placeholder image paths and temporary alt text, then outputs a table of camelCase filenames you need to provide (e.g., clusteredLighting.jpg, frameGraph.jpg, sdfText.jpg).
Between passes — Capture screenshots manually:
Visit each demo link from the blog post and take a screenshot.
Save each screenshot to src/content/featureDemos/assets/img/ using the exact filename from the table.
Pass 2 — Generate alt text:
Ask Copilot: "Add alt tags to the feature demos page."
The alt text skill views each image and writes descriptive alt text based on what the screenshot actually shows.
Alt Text Generation
The alt text skill works on any page — not just the homepage. Ask Copilot to add or fix alt tags on any page, and it will find images with missing, empty, or placeholder alt text, view each image file, and write descriptive text.
Examples:
"Add alt tags to the main page"
"Fix alt tags on the feature demos page"
"Update alt text on the community page"
Available Scripts
Script
Command
Description
Process all images
npm run process-images
Resize, optimize, and sample background colors for all feature images
this property available as part of page level Json property
"title": "BabylonJS - 3D engine based on WebGL/Web Audio and JavaScript"
Meta tags
meta tags can be unique for each page. This property available as part of page level Json property and contains list of tags
"metaTags": [
{
"name": "description",
"content": "BabylonJS - 3D engine based on WebGL/Web Audio and JavaScript"
},
{
"property": "og:title", //optional property for open graph
"content": "BabylonJS - 3D engine based on WebGL/Web Audio and JavaScript"
}
]
The most recent commit recorded on BabylonJS/Website was 13 days ago, based on the GitHub push timestamp. The repository has 252 forks — one of the better signals of community interest.
How does BabylonJS/Website compare to other Frontend projects?
BabylonJS/Website is tracked by TopGit in the Frontend category, with 217 GitHub stars and written in JavaScript. Browse the Frontend topic page on TopGit to compare it against similar projects by stars and activity.
How many stars does BabylonJS/Website have?
BabylonJS/Website has 217 GitHub stars — refresh the page for the live number, or check github.com/BabylonJS/Website. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
Is BabylonJS/Website open source?
TopGit's metadata for BabylonJS/Website does not record a license. Most public repositories on GitHub ARE open source, but the exact terms vary — verify by opening the LICENSE file directly.
What is BabylonJS/Website?
BabylonJS/Website (BabylonJS/Website) is a JavaScript project on GitHub. From the project's own README: Main babylon.js website
Where do I read more about BabylonJS/Website?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/BabylonJS/Website is the definitive source.
Read full README in the tab above.
Want a second opinion on Website?
Ask an AI that can read this page — one click and you get its take on Website.