abathur / ldmud-doc

A temporary repo for working on a revamp of the documentation system for http://github.com/ldmud/ldmud

abathur/ldmud-doc Issues

Linter-enforced plaintext format rules/standards...
Updated 7 years ago
more thoroughly defined/documented grammar?
Updated 9 years ago
Do we need to include <version>vs<version> docs in the parsed/generated output?
Updated 9 years ago
grammar/semantic specifics for documenting history
Closed 8 years ago3
Version ordering, separation and multi-version change notes in HISTORY sections?
Closed 8 years ago1
Do we want to preserve prose-based history sections?
Closed 9 years ago1
documenting function arguments
Updated 9 years ago
How should document status be presented?
Updated 8 years ago1
clearly defined document "status" headers (OPTIONAL, etc.)
Closed 8 years ago2
how document/code "status" is handled
Closed 8 years ago1
should the content of call_other be split?
Closed 8 years ago2
Why is array/string-indexing documentation (efun/[]) located in efun instead of LPC?
Closed 9 years ago2
synopsis grouping
Closed 9 years ago1
usage v. example section consistency/semantics
Closed 8 years ago2
limiting the nouns we use for notes/caveats/admonitions, and defining clear semantics for them
Closed 9 years ago5
BUGS/NOTE/ETC. presentation
Closed 8 years ago8
document (perhaps code?) metadata
Closed 9 years ago2
alignment of synopsis parts
Closed 9 years ago3
Should the source be line-wrapped?
Closed 9 years ago3