Skip to content

docs: move user documentation into docs/ for website hosting - #145

Merged
wu-sheng merged 1 commit into
masterfrom
docs/host-docs-on-website
Aug 15, 2026
Merged

docs: move user documentation into docs/ for website hosting#145
wu-sheng merged 1 commit into
masterfrom
docs/host-docs-on-website

Conversation

@wu-sheng

Copy link
Copy Markdown
Member

Motivation

All Node.js Agent documentation lived in a single ~190-line README.md, so it could not be imported by the SkyWalking website like the Python, Go, and Rust agent docs are. This splits it into a docs/ tree the website can render.

What changed

  • docs/README.md — overview page (/readme in the sidebar), docs/menu.yml — website sidebar.
  • docs/en/ — 14 pages: setup (quick start, configuration, start and stop), features (tracing, runtime metrics), plugins (supported libraries, AWS SDK v2), advanced use (serverless, webpack, troubleshooting), contribution (build and test, plugin development, release).
  • README.md — now a short entry point: requirements, install, quick start, links into docs/.
  • CONTRIBUTING.md — points at the build, plugin development, and release guides.
  • docs/How-to-release.md — kept as a stub with the #vote-check heading, so the footnote in previously sent [VOTE] emails still lands somewhere useful.
  • scripts/release.sh — the [VOTE] email now cites in-tarball doc paths (docs/ ships inside the source package), replacing links to a CONTRIBUTING.md anchor that this PR removes.

Layout follows apache/skywalking-python and apache/skywalking-go.

Accuracy

Content was checked against the source rather than copied forward:

  • Every SW_* variable read anywhere in src/ is documented, and nothing is documented that the agent does not read.
  • Two long-standing README errors are corrected: SW_AGENT_INSTANCE defaults to the host name (not a random value, AgentConfig.ts), and SW_AGENT_LOGGING_LEVEL defaults to error (not info, logging/index.ts).
  • SW_AGENT_TRACE_TIMEOUT is documented as the gRPC deadline for trace reports, meter reports, and service management requests, which is where it is actually used.
  • Meter table, webpack static-loader plugin list, AWS SDK v2 plugin behavior, and the build/test commands match src/ and .github/workflows/test.yaml.

Follow-up

Rendering on the website needs a companion PR in apache/skywalking-website adding repoUrl and a Next entry for the Node.js Agent in data/docs.yml — without repoUrl the doc importer skips the repository.

🤖 Generated with Claude Code

Split the README into a docs/ tree that the SkyWalking website can import,
following the layout used by the Python and Go agents (docs/README.md as the
overview page, docs/menu.yml as the sidebar, pages under docs/en/).
- README.md becomes a short entry point: requirements, install, quick start,
and links into docs/.
- CONTRIBUTING.md points at the build, plugin development, and release guides.
- docs/en/ adds setup (quick start, configuration, start and stop), features
(tracing, runtime metrics), plugins (supported libraries, AWS SDK v2),
advanced use (serverless, webpack, troubleshooting), and contribution
(build and test, plugin development, release) pages.
- docs/How-to-release.md stays as a stub, keeping the #vote-check anchor that
earlier [VOTE] emails link to.
- scripts/release.sh: the [VOTE] email now points at the in-tarball doc paths,
since the moved guides ship inside the source package.
Configuration values, meter names, plugin behavior, and the build and test
commands were verified against src/ and .github/workflows/test.yaml. Two
long-standing README errors are corrected: SW_AGENT_INSTANCE defaults to the
host name (not a random value) and SW_AGENT_LOGGING_LEVEL defaults to error
(not info).
The website side needs a follow-up PR in apache/skywalking-website adding
repoUrl and a Next entry for the Node.js Agent in data/docs.yml.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@wu-shengwu-sheng added this to the 0.10.0 milestone Aug 15, 2026
@wu-shengwu-sheng added the documentation Improvements or additions to documentation label Aug 15, 2026
@wu-sheng
wu-sheng merged commit 9642d74 into masterAug 15, 2026
37 checks passed
@wu-sheng
wu-sheng deleted the docs/host-docs-on-website branch August 15, 2026 15:34
wu-sheng added a commit to apache/skywalking-website that referenced this pull request Aug 16, 2026
skywalking-nodejs moved its user documentation into docs/ with a menu.yml
(apache/skywalking-nodejs#145), so the agent can render on the site like
every other Hugo-hosted component instead of linking out to a GitHub tree.
Adds repoUrl and the Next/Latest/v0.9.0 entries. Next tracks master
(0.10.0-dev). Latest and v0.9.0 both pin bf5dc68 on the 0.9.0-docs branch,
which is the v0.9.0 tag commit plus the docs move; a follow-up commit there
removes what landed after the release, so the snapshot documents the agent
users actually run. Sharing one commitId between Latest and v0.9.0 also lets
seo/doc-canonical-map.html point the tagged tree at /latest/.
The old GitHub-tree entry could not be kept alongside these: repoUrl is
item-level, so docs.js runs every entry through doc.sh, and an external link
has no docs/menu.yml to copy. The version switcher likewise builds its target
by substituting the slug into /docs/<repo>/<version>/, so it cannot reach
github.com. Nothing is lost — at v0.9.0 docs/ held only How-to-release.md,
and the docs card already links to the repository.
Verified with a full npm run docs && hugo: 5421 pages, all three trees
rendered, runtime-metrics present only under next.
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentationImprovements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@wu-sheng@kezhenxu94