Editorial updates of documentation#1171
Conversation
tgreenx
left a comment
There was a problem hiding this comment.
I suggest to include this PR in 2023.1.1.
tgreenx
left a comment
There was a problem hiding this comment.
I did another pass through all README.md and other main documents in docs/public/ and found the following nits below. Moreover I think the file WISHLIST.md can be updated: items 2, 3, 4, 8 (soonTM) can all be removed, possibly items 5 and 6 too.
Additional changes suggestions:
The the -> Then the
zonemaster/docs/public/using/README.md
Line 17 in c7c6793
This if -> This is
do -> does
not with -> not work with
zonemaster/test-zone-data/README.md
Line 24 in c7c6793
Adress-TP -> Address-TP
zonemaster/test-zone-data/README.md
Line 136 in c7c6793
| - [DNSSEC-TP](specifications/test-zones/DNSSEC-TP) | ||
| - [Nameserver-TP](specifications/test-zones/Nameserver-TP) | ||
| - [Zone-TP](specifications/test-zones/Zone-TP) |
There was a problem hiding this comment.
Such entries will prevent building the documentation. They should link to a document not a folder.
There was a problem hiding this comment.
Will fix by including READMEs.
| *Click on [SUMMARY](../SUMMARY.md) to view a linked tree structur of all documents | ||
| under "public".* |
There was a problem hiding this comment.
This will create a broken link when building the HTML documentation. The SUMMARY.md file won't have any HTML counterpart. I suggest removing this paragraph (and all similar paragraphs in the other documents).
There was a problem hiding this comment.
Is the name SUMMARY.md magic? If I create a symlink TREE.md --> SUMMARY.md will then TREE.md get an HTML counterpart?
I really want to use the SUMMARY.md since it is very helpful for the users instead walking through the README.md files.
There was a problem hiding this comment.
No there is no magic, as the documentation says: "The summary file is used by mdBook to know what chapters to include, in what order they should appear, what their hierarchy is and where the source files are. Without this file, there is no book."
In order to have an HTML file, you need to list the Markdown file into SUMMARY.md. And currently, I don't feel at ease with listing SUMMARY.md into itself.
There was a problem hiding this comment.
I understand what you mean, but the SUMMARY file is really useful when navigating in the document tree. I think it would be wrong to hide it for the readers in Github.
There was a problem hiding this comment.
The new docs/public/README.md is not included in SUMMARY.md and I guess that it does not have to be included, and then I can keep the link in that README, but remove it from the other READMEs.
There was a problem hiding this comment.
Now that I better understand how it works I can see that there were some documents under specification/test-zones that were missing.
There was a problem hiding this comment.
Well it could be an idea to include the docs/public/README.md to the SUMMARY.md file. In this way, the landing page would be this README file.
diff --git a/docs/public/SUMMARY.md b/docs/public/SUMMARY.md
index 33738dda..86fa3090 100644
--- a/docs/public/SUMMARY.md
+++ b/docs/public/SUMMARY.md
@@ -2,6 +2,7 @@
https://rust-lang.github.io/mdBook/format/summary.html -->
# Documents in public document tree
+- [Introduction](README.md)
- [Installation](installation/README.md)
- [Prerequisites](installation/prerequisites.md)
- [Zonemaster-LDNS](installation/zonemaster-ldns.md)There was a problem hiding this comment.
If docs/public/README.md is included in SUMMARY.md then it cannot link to SUMMARY.md. I prefer to have it this way. I really want to be able to link to SUMMARY.md for Github users.
|
I changed the milestone to v2023.1.1, as discussed in our latest meeting. |
That is fine. I was waiting for the final approval. I changed the base branch to release-branch-v2023.1.1. |
| 3. Developing a Mobile app | ||
| 4. Parallel tests | ||
| 5. It would be nice to test if unknown RR types can be queried (Ref : | ||
| https://savannah.nongnu.org/bugs/?36909) |
There was a problem hiding this comment.
Item number 5 in this wish list is something that could be implemented in a reasonable amount of time. Do we have an issue on the zonemaster-engine repo for this?
There was a problem hiding this comment.
I can see that there was one, which was (surprisingly) opened for only a few days: #323
|
|
||
| ## Elaboration of the Test Case | ||
|
|
||
| Test cases are written for almost all Test Requirement. There could be the case |
There was a problem hiding this comment.
| Test cases are written for almost all Test Requirement. There could be the case | |
| Test cases are written for almost all Test Requirements. There could be the case |
|
@PNAX, @tgreenx and @marc-vanderwal, please re-review. |
| 3. Developing a Mobile app | ||
| 4. Parallel tests | ||
| 5. It would be nice to test if unknown RR types can be queried (Ref : | ||
| https://savannah.nongnu.org/bugs/?36909) |
There was a problem hiding this comment.
I can see that there was one, which was (surprisingly) opened for only a few days: #323
marc-vanderwal
left a comment
There was a problem hiding this comment.
Looks good to me.
Purpose
Changes
and several other files.
How to test this PR
Review.