https://github.com/chris-n-k/napari-docs
Documentation for napari (other than API docs)
Science Score: 23.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
○CITATION.cff file
-
○codemeta.json file
-
○.zenodo.json file
-
✓DOI references
Found 1 DOI reference(s) in README -
✓Academic publication links
Links to: zenodo.org -
○Academic email domains
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (13.6%) to scientific vocabulary
Last synced: 10 months ago
·
JSON representation
Repository
Documentation for napari (other than API docs)
Basic Info
- Host: GitHub
- Owner: Chris-N-K
- License: bsd-3-clause
- Language: Makefile
- Default Branch: main
- Size: 31.8 MB
Statistics
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
- Releases: 0
Fork of napari/docs
Created over 3 years ago
· Last pushed over 3 years ago
https://github.com/Chris-N-K/napari-docs/blob/main/
# napari docs This repository contains the sources for the napari documentation. This includes tutorials, how-tos and other narrative documentation. The autogenerated API documentation is extracted from the source code docstrings, which live on https://github.com/napari/napari ## mission, values, and roadmap For more information about our plans for `napari` you can read our [mission and values statement](https://napari.org/community/mission_and_values.html), which includes more details on our vision for supporting a plugin ecosystem around napari. You can see details of [the project roadmap here](https://napari.org/roadmaps/index.html). ## contributing Contributions are encouraged! Please read our [contributing guide](https://napari.org/developers/contributing.html) to get started. Given that we're in an early stage, you may want to reach out on our [Github Issues](https://github.com/napari/napari/issues) before jumping in. ## code of conduct `napari` has a [Code of Conduct](https://napari.org/community/code_of_conduct.html) that should be honored by everyone who participates in the `napari` community. ## governance You can learn more about how the `napari` project is organized and managed from our [governance model](https://napari.org/community/governance.html), which includes information about, and ways to contact the [@napari/steering-council and @napari/core-devs](https://napari.org/community/team.html#current-core-developers). ## citing napari If you find `napari` useful please cite [this repository](https://github.com/napari/napari) using its DOI as follows: > napari contributors (2019). napari: a multi-dimensional image viewer for python. [doi:10.5281/zenodo.3555620](https://zenodo.org/record/3555620) Note this DOI will resolve to all versions of napari. To cite a specific version please find the DOI of that version on our [zenodo page](https://zenodo.org/record/3555620). The DOI of the latest version is in the badge at the top of this page. ## help We're a community partner on the [image.sc forum](https://forum.image.sc/tags/napari) and all help and support requests should be posted on the forum with the tag `napari`. We look forward to interacting with you there. Bug reports should be made on our [github issues](https://github.com/napari/napari/issues/new?template=bug_report.md) using the bug report template. If you think something isn't working, don't hesitate to reach out - it is probably us and not you! ## institutional and funding partners 
Owner
- Name: Christopher Nauroth-Kreß
- Login: Chris-N-K
- Kind: user
- Location: Würzburg, Germany
- Company: University Hospital Würzburg - Institute of Neuroradiology
- Repositories: 3
- Profile: https://github.com/Chris-N-K
PhD Candidate, MSc Biosciences