Closed natsukagami closed 8 months ago
I wonder what's the role of the README in this setup: Build instructions are in CONTRIBUTING and infos - or rather: links - are on the docs page. If the page didn't look as nice as it does, I would have voted for its deletion in favor of an elaborate README. But I guess it's fine, because it does look nice :)
Besides, I would add some "For an overview of the library, see..." which would be really important to be in the docs imho. We do have something like that: the release notes: https://github.com/lampepfl/gears/releases/tag/v0.1.0. Maybe we could copy/move them to the docs - and in any case keep them updated. Otherwise it's very hard to get started, given the reports, the Scala API, and the increasingly outdated Scalar README.
I think it would be better to have more parts on the README even if they are available somewhere else, the following are the parts I find useful:
In my opinion, the README of the following pages looks fine to me and is similar to gears (in some way :D):
The page is great. I think the library is better to have its own logo :D
Besides, I would add some "For an overview of the library, see..." which would be really important to be in the docs imho.
Would the book be sufficient in this case?
Let's have this in first -- I think it's better to have a landing page first and foremost, better than nothing ;) We can improve it later.
Most documentations live in
/docs
now, with a landing page at https://lampepfl.github.io/gears linking to them.README now is a simple page showing build status, release, basic build instructions etc.