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

Documentation #24

Open
apdavison opened this issue Aug 8, 2019 · 1 comment
Open

Documentation #24

apdavison opened this issue Aug 8, 2019 · 1 comment
Labels
enhancement New feature or request

Comments

@apdavison
Copy link
Member

We need documentation for three classes of user:

  1. viewers - just want to look at the data
  2. website developers - want to embed the component in their website
  3. service hosts - want to deploy their own instance of the REST API service

Decision needed: where to host each type of documentation, and whether to have all documentation in one place (simpler but potentially confusing) or separate.

@xgui3783
Copy link

xgui3783 commented Aug 8, 2019

I would argue that:

1/ on https://neo-viewer.bransimulation.eu
2/ on https://neo-viewer.bransimulation.eu and github
3/ on https://neo-viewer.bransimulation.eu and github (and ReadTheDocs? Coming from the non-python background, I often find myself on github for documentations)

It probably does not hurt to have hyper links (e.g. on github, a link pointing to neo-viewer.brainsimulation.eu for users who just want to look at data)

If the documentation is in markdown/rst, github can automatcially display them formatted. Turning them into HTML pages should be relatively simple, too.

@apdavison apdavison added the enhancement New feature or request label Aug 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants