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

Revamp readme #335

Closed
jcoupey opened this issue Apr 30, 2020 · 4 comments
Closed

Revamp readme #335

jcoupey opened this issue Apr 30, 2020 · 4 comments

Comments

@jcoupey
Copy link
Collaborator

jcoupey commented Apr 30, 2020

The current readme is, hum, quite sparse on information. Considering this is the entry point for the project on GitHub, it should be improved to contain more high-level information and pointers to other resources. What should be added:

  • supported problem types
  • more detail on features
  • supported routing engines
  • the kind of tests we have in place (CI builds, runs on various benchmarks)
  • more on how to get started
  • ...
@jcoupey jcoupey added this to the v1.7.0 milestone Apr 30, 2020
@jcoupey jcoupey self-assigned this Apr 30, 2020
@nilsnolde
Copy link
Contributor

+1000 :)

Also it's confusing that there's a docs directory where the API is documented, which IMHO belongs in the wiki. I look at that like 3 times a year and can never find it;)

@jcoupey
Copy link
Collaborator Author

jcoupey commented Apr 30, 2020

I think it makes sense that the API documentation is somehow versioned along with the code so it's always consistent with whatever version is checked out. Maybe what you point out comes down to making things more clear from the wiki?

Currently the Usage page on the wiki simply links to specific versions for the docs. One option would be to have a dedicated "Documentation" page in the wiki for the last release where we paste the docs (and specify the version).

@nilsnolde
Copy link
Contributor

nilsnolde commented Apr 30, 2020

I think it makes sense that the API documentation is somehow versioned along with the code

Yeah, you're right of course.

Currently the Usage page on the wiki simply links to specific versions for the docs

OMG, I really am blind.. That's my bad, sorry. Maybe just not "TL;DR", but "API documentation" as header. Then even I might see that there's actually a link to it;)

@jcoupey
Copy link
Collaborator Author

jcoupey commented May 2, 2020

Hopefully the README is now more useful.

@jcoupey jcoupey closed this as completed Jun 24, 2020
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

2 participants