issues
search
abathur
/
ldmud-doc
A temporary repo for working on a revamp of the documentation system for http://github.com/ldmud/ldmud
0
stars
0
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Linter-enforced plaintext format rules/standards...
#19
abathur
opened
7 years ago
0
more thoroughly defined/documented grammar?
#18
abathur
opened
8 years ago
0
Do we need to include <version>vs<version> docs in the parsed/generated output?
#17
abathur
opened
8 years ago
0
grammar/semantic specifics for documenting history
#16
abathur
closed
7 years ago
3
Version ordering, separation and multi-version change notes in HISTORY sections?
#15
abathur
closed
7 years ago
1
Do we want to preserve prose-based history sections?
#14
abathur
closed
8 years ago
1
documenting function arguments
#13
abathur
opened
8 years ago
0
How should document status be presented?
#12
abathur
opened
8 years ago
1
clearly defined document "status" headers (OPTIONAL, etc.)
#11
abathur
closed
7 years ago
2
how document/code "status" is handled
#10
abathur
closed
7 years ago
1
should the content of call_other be split?
#9
abathur
closed
7 years ago
2
Why is array/string-indexing documentation (efun/[]) located in efun instead of LPC?
#8
abathur
closed
8 years ago
2
synopsis grouping
#7
abathur
closed
8 years ago
1
usage v. example section consistency/semantics
#6
abathur
closed
8 years ago
2
limiting the nouns we use for notes/caveats/admonitions, and defining clear semantics for them
#5
abathur
closed
8 years ago
5
BUGS/NOTE/ETC. presentation
#4
abathur
closed
8 years ago
8
document (perhaps code?) metadata
#3
abathur
closed
8 years ago
2
alignment of synopsis parts
#2
abathur
closed
8 years ago
3
Should the source be line-wrapped?
#1
abathur
closed
8 years ago
3