Skip to content
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

User-friendly README #221

Closed
Expander opened this issue May 18, 2020 · 1 comment
Closed

User-friendly README #221

Expander opened this issue May 18, 2020 · 1 comment
Assignees

Comments

@Expander
Copy link
Member

Over time, our README.rst has grown to a large file with lots of installation/build instructions for developers. OTOH, the part that contains physics/application-related information is significantly smaller. I think it is time so improve that and clean-up or split the README.rst file.

My first proposal would be to reduce the size of the README.rst file and introduce more links to sub-pages for more details. We may think about the following structure:

  1. Quick start (similar to what we currently have)
  2. Build instructions (very short or link to separate doc/build.rst file)
  3. Usage examples (short script or physics examples or links to sub-pages)
    a) Predefined models
    b) Creating new models
  4. References

What is your opinion?

@pathron
Copy link
Member

pathron commented May 18, 2020

Actually just today I was there wasn’t enough content :) though this is not really disagreeing with you because we can also add some additional documentation in sub pages. For the sake of an honours student project I was looking up how Himalaya is used, but the details are not in the README so I ended up looking at our FS2 manual.

So anyway my vote is short sections with the parts you describe, but with links to other pages. Unfortunately a lot of people will just view the README with less of whatever, so they will miss the links, but not sure there is anything more we can do about that other than clearly state further documentation is in the doc directory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants