-
Notifications
You must be signed in to change notification settings - Fork 12
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
My first pass in updating use-case documentation #12
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've got one link syntax fix (I'll commit it), and a question.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not sure why i had to review this..
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@wesleyboar you can see here that I had to add
OpenSees Model Calibration
plus, the single # in the first line of the original file, which was his title, messed up the hierarchy
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, okay. I am familiar with that problem (from TACC-Docs). Thanks for the reminder.
After my work, I'll be comfortable showing you how we can include documents with lower or higher level heading hierarchies, yet still render in nav appropriately.
Are we now just waiting for @susanunit to approve? |
Apologies for the delay. Approved. |
Thank you, Susan for the approval. |
I have made significant updates to the seismic use cases.
I have also updated the wind cases.