Follow-up from "[web] Finished docs for release"
The following discussions from !22 (merged) should be addressed:
-
@chleh started a discussion: (+2 comments) This page currently is both the landing page for ogstools and the start of the ogstools documentation. Therefore, I'd drop the heading and reorder the paragraphs.
I'm not sure about the date and version line. Will the documentation page be linked to the version on Pypi or will it be linked to the master branch? Will both versions always be in sync? Will we hit some rate limits on Pypi? If we stick to the master branch, will the version refer to the git tag, such as
6.4.3-750-g9f18299f5c
for OGS?`ogstools` is a collection of Python tools aimed at evolving into a modeling toolchain around [OpenGeoSys](https://www.opengeosys.org), a finite element solver for coupled thermo-hydro-chemo-mechanical problems in the subsurface. In this project we’ll collect existing pre and postprocessing scripts for OpenGeoSys at first. Over time we’ll develop an entire toolchain out of that collection. Currently we are at the stage of code collection. **Date:** {sub-ref}`today` **Version:** {sub-ref}`version` **Useful links:** [Source repository](https://gitlab.opengeosys.org/ogs/tools/ogstools) | [Issues](https://gitlab.opengeosys.org/ogs/tools/ogstools/-/issues) | [OpenGeoSys Website](https://www.opengeosys.org) | [OpenGeoSys Forum](https://discourse.opengeosys.org)
-
@chleh started a discussion: In the future we might add a section listing important projects we depend on. PyVista, meshio, gmsh, matplotlib, numpy, ...