About this demo

What this site is, what it isn't, and where the content comes from.

What this is

This site is a fan-made, unofficial demo. It exists to answer one question concretely: what does it take to give a Salesforce open-source project a modern, searchable, AI-ready docs site? The answer, it turns out, is a Markdown folder and one CLI tool — Blume.

It is not affiliated with, endorsed by, or produced by the maintainers of Nebula Logger.

What this isn’t

This is not a replacement for the official documentation. For anything authoritative — installation, releases, issues, the full wiki — go straight to the source:

jongpie/NebulaLoggerThe most robust observability solution for Salesforce experts. Built 100% natively on the platform, and designed to work seamlessly with Apex, Lightning Components, Flow, OmniStudio, and integrations.952240

Nebula Logger on GitHub

The real repository, actively maintained by Jonathan Gillespie and contributors.

Official docs

The maintainer’s own documentation site.

Attribution & license

All technical content reproduced across this demo (feature descriptions, code samples, API names) is adapted from the Nebula Logger README, © Jonathan Gillespie and contributors, released under the MIT License. The MIT License permits reuse and adaptation like this, provided the original copyright notice and license are retained — see ATTRIBUTION.md in the root of this repository for the full notice and license text.

Nebula Logger itself is 100% free and open source. If your team ends up using it after reading this, the right next step is installing the real package from the real repo, not this one.

How this was built

Pulled the real source

The real Nebula Logger README, wiki, and public docs, cloned locally as raw source material.

Reorganized around three audiences

Developers, admins, and architects, instead of one long linear page — that’s how Salesforce teams actually divide up this kind of work.

Built with Blume

Ran npx blume init, dropped the content in as .mdx files, and used Blume’s built-in Tabs, CodeGroup, CardGroup, Panel, TypeTable, and GithubInfo components with zero custom components written.

Deployed as a static site

No server, no CMS, no ongoing maintenance beyond editing Markdown.

A published mistake, fixed in the open

The first version of this site’s README overstated two numbers. Both were caught by independent review after publishing, not before:

39 pages is the real count (6 start-here + 26 guides + 7 reference). 53 Apex classes is the real count, verified by cloning the actual project and counting its own generated ApexDocs output module by module — the 148 figure had never been checked against anything before it shipped. The commit that fixed both is public, same as the mistake was.