| commit | 6a469c10545cd419a1622382f1f1ae01623ebb08 | [log] [tgz] |
|---|---|---|
| author | Alex Eagle <eagle@post.harvard.edu> | Wed Oct 29 14:53:09 2025 -0700 |
| committer | GitHub <noreply@github.com> | Wed Oct 29 17:53:09 2025 -0400 |
| tree | c061facc0dc264fafd96b8703d8fcc70bb2a2569 | |
| parent | c086e251a73b6ff53c2d83445ebd690b20e72a39 [diff] |
chore: readme point to BCR-hosted docs (#306) The rules-template no longer recommends using Stardoc.
Stardoc is a documentation generator for Bazel APIs such as custom rules written in Starlark.
Stardoc provides a Bazel rule (stardoc, see documentation) that can be used to generate Markdown documentation for Starlark rules. Stardoc generates one documentation page per .bzl file.
Stardoc runs a Velocity template on the output of the native.starlark_doc_extract rule.
Modules published to the Bazel Central Registry do not need to use Stardoc. They can simply publish the starlark_doc_extract outputs as a release artifact. See https://github.com/bazelbuild/bazel-central-registry/blob/main/docs/stardoc.md.
Stardoc is a replacement for the deprecated “Skydoc” documentation generator.
See Skydoc Deprecation for details on the deprecation and migration details.
See our future plans for refactoring Stardoc to be more consistent with how Bazel evaluates .bzl files, and what it means for maintenance of this project.
See the maintaner's guide for instructions for cutting a new release.