It would be best for users if the documentation for the verification, benchmarking, and validation cases all pointed to the input file corresponding to the results shown in the documentation.
Design
Add the following section in the documentation page of verification and validation cases:
### Input file
!style halign=left
The input file for this case can be found at [/input_file_name.i].
As @cticenhour suggested in #146, we could use the listing extension to display the whole input in a scrollable code box. But that is optional, since clicking this link will also open a scrollable modal with a code box.
Impact
Better documentation and experience for the users, and more transparency.
Reason
It would be best for users if the documentation for the verification, benchmarking, and validation cases all pointed to the input file corresponding to the results shown in the documentation.
Design
Add the following section in the documentation page of verification and validation cases:
As @cticenhour suggested in #146, we could use the
listingextension to display the whole input in a scrollable code box. But that is optional, since clicking this link will also open a scrollable modal with a code box.Impact
Better documentation and experience for the users, and more transparency.