When visitors land on our community website the first content they see is a link to our fledgling documentation pages. The purpose of this separate documentation site is to be the “root” of all documentation related to the MUSES framework. In other words, it does not need to include all content, but it should provide a direct minimal-length chain of links to all technical documentation.
Example: Researcher finds a list of code modules supported by MUSES on the root documentation site → They follow a link to one of the code module’s git repo → They discover the code module’s “root document” in the form of the
Readme.md file in the git repo.
The project documentation is a dynamic, living organism. As MUSES collaborators add code modules and the system evolves, each of us share a responsibility to add and update content related to our components.
I encourage everyone to take a few minutes to visit our community landing page and imagine you are a scientist who has vaguely heard of MUSES and is interested in learning what it can offer them. What would this person learn by browsing the website? What would they learn about the existing code modules? What would they think is being actively developed? Would they know how to contact someone with questions if they were interested in learning more?