-
Notifications
You must be signed in to change notification settings - Fork 169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reorganize appendices #1204
Comments
I generally agree, but would it be worth breaking a lot of links? |
Maybe we could forward the current URLs to the new ones automatically? I'm not sure how to do that in mkdocs, but if it's possible then that would solve the problem. |
It looks like there's a |
Do we want to drop the |
Should the glossary be part of the main specification? |
I would say yes but maybe you have some alternative in mind. |
I was just thinking that the glossary should be more easily accessible (i.e., a chapter in the main specification instead of an appendix), but I don't know if others feel the same way. As we start to link more terms in the main text to glossary items, it seems like the glossary should become more of a central part of the spec. |
hahaha. I had understood the opposite of what you implied: that you wanted to take it completely out of the spec and make it standalone as if it was not related to the spec. I am tired... But yeah I would not mind making it more central. |
sound like a good idea to me! |
Here is the current order:
I think we should reorganize it so that it moves from more general topics to more specific. For example, the glossary should be close to the top, along with general specification principles like entity descriptions and units.
The text was updated successfully, but these errors were encountered: