WalkLang Documentation
WalkLang docs are built into a static site for walklang.wlkrlabs.com/docs. This directory remains the source for the hosted documentation path.
Use this page as the docs front door. The root README explains the repository; these docs explain how to install, learn, use, verify, and evolve WalkLang.
Get Started
Use The Language
- Language concepts and docs standard
- Standard library
- Diagnostics and warnings
- Compatibility promise
- Migration guide
- Deprecation policy
Use The Tools
- Project mode and packages
- Editor tooling, LSP, docs generation, and debug maps
- Runtime and backend model
- Draft networking
- Rich runtime tracks
- Architecture
Current Version
WalkLang is currently v6.3.3. That single project version covers the compiler, tooling, backend, release artifacts, docs, and implemented language surface.
Features inside v6.3.3 use maturity labels:
- stable: core syntax, diagnostics, modules, tests, and standard-library helpers
- draft:
do:,defer:,io,parse,process,file,dir,path, - experimental: structs, methods, and simple generic functions
- standard platform:
walktopis the first official standalone
json, map, term, http, and html
WalkLang-built CLI tool
Project Direction
- Roadmap
- Systems compiler port plan
- Standard platform
- Explicit systems track
- Design rules
- Purpose
- Docs style guide
Generated Reference Docs
WalkLang supports rustdoc-style structured comments on public symbols. Generate Markdown and JSON reference output from real source with:
scripts/build-docs-site.sh
Reference docs under docs/reference/ are generated artifacts. The static site under public/ publishes the rendered docs pages, generated API reference, raw Markdown, and api.json from the same compiler output.
Hosting Contract
The public docs home is configured for:
walklang.wlkrlabs.com/docs
The public scheme is HTTPS, and HTTP redirects to HTTPS. docs/STATUS.md records the latest checked live HTTP/HTTPS state.
Use stable, relative links inside this directory so the same Markdown works in GitHub and on the hosted site. Run scripts/check-docs-site.sh before publishing docs changes.