@@ -9,25 +9,49 @@ helps, and credit will always be given.
99
1010If you are reporting a bug, please include:
1111
12- * Your operating system name and version.
13- * Any details about your local setup that might be helpful in troubleshooting.
14- * Detailed steps to reproduce the bug.
12+ * Your operating system name and version
13+ * Python version
14+ * Any details about your local setup that might be helpful in troubleshooting
15+ * Detailed steps to reproduce the bug
1516
1617### Fix Bugs
1718
18- Look through the GitHub issues for bugs. Anything tagged with "bug" and "help
19- wanted" is open to whoever wants to implement it.
19+ Look through the [ GitHub issues] ( https://github.com/biomarkersParkinson/paradigma/issues ) for bugs.
20+ Anything tagged with ` bug ` or ` help wanted` is open to whoever wants to implement it.
2021
2122### Implement Features
2223
23- Look through the GitHub issues for features. Anything tagged with "enhancement"
24- and " help wanted" is open to whoever wants to implement it.
24+ Look through the [ GitHub issues] ( https://github.com/biomarkersParkinson/paradigma/issues ) for features.
25+ Anything tagged with ` enhancement ` or ` help wanted ` is open to whoever wants to implement it.
2526
2627### Write Documentation
2728
28- You can never have enough documentation! Please feel free to contribute to any
29- part of the documentation, such as the official docs, docstrings, or even
30- on the web in blog posts, articles, and such.
29+ Documentation contributions are always welcome! You can contribute to:
30+ * Official docs: Located in ` docs/ `
31+ * Tutorial notebooks: ` docs/tutorials/ `
32+ * Docstrings: In Python modules
33+ * Articles or blog posts
34+
35+ #### Workflow for notebooks and docs:
36+ 1 . Run and export notebooks:
37+
38+ ``` bash
39+ poetry run build-docs
40+ ```
41+
42+ This will:
43+ * Execute all notebooks in ` docs/tutorials/ `
44+ * Export them to Markdown in ` docs/tutorials/_static/ `
45+ * Strip outputs
46+ * Build the HTML documentation
47+
48+ 2 . Serve documentation locally:
49+
50+ ``` bash
51+ poetry run serve-docs
52+ ```
53+
54+ This will serve the built HTML at ` http://localhost:8000 ` .
3155
3256### Submit Feedback
3357
@@ -36,28 +60,49 @@ If you are proposing a feature:
3660* Explain in detail how it would work.
3761* Keep the scope as narrow as possible, to make it easier to implement.
3862* Remember that this is a volunteer-driven project, and that contributions
39- are welcome :)
63+ are welcome!
4064
4165## Get Started!
4266
43- Ready to contribute? Here's how to set up ` paradigma ` for local development.
67+ Ready to contribute? Here's how to set up ` paradigma ` locally:
68+ 1 . Clone the repository:
69+
70+ ``` bash
71+ git clone https://github.com/biomarkersParkinson/paradigma.git
72+ cd paradigma
73+ ```
74+
75+ 2 . Install dependencies via Poetry:
76+
77+ ``` bash
78+ poetry install
79+ ```
80+
81+ 3 . Create a new branch for your work:
82+
83+ ``` bash
84+ git checkout -b name-of-your-bugfix-or-feature
85+ ```
4486
45- 1 . Download a copy of ` paradigma ` locally.
46- 2 . Install ` paradigma ` using ` poetry ` :
87+ 4 . Make your changes and run the pre-commit hooks:
4788
48- ``` console
49- $ poetry install
50- ```
89+ ``` bash
90+ pip install pre-commit
91+ pre-commit install
92+ pre-commit run --all-files
93+ ```
5194
52- 3. Use `git` (or similar) to create a branch for local development and make your changes:
95+ This ensures code formatting (` black ` ), import sorting (` isort ` ), stripping notebook outputs, and other checks.
96+ These pre-commit hooks also run for changed and staged files when committing.
5397
54- ```console
55- $ git checkout -b name-of-your-bugfix-or-feature
56- ```
98+ 5 . If contributing to docs, build and serve them locally to verify:
5799
58- 4. When you're done making changes, check that your changes conform to any code formatting requirements and pass any tests.
100+ ``` bash
101+ poetry run build-docs
102+ poetry run serve-docs
103+ ```
59104
60- 5 . Commit your changes and open a pull request.
105+ 6 . Commit your changes and open a pull request.
61106
62107## Pull Request Guidelines
63108
@@ -70,4 +115,5 @@ Before you submit a pull request, check that it meets these guidelines:
70115## Code of Conduct
71116
72117Please note that the ` paradigma ` project is released with a
73- Code of Conduct. By contributing to this project you agree to abide by its terms.
118+ [ Code of Conduct] ( https://biomarkersparkinson.github.io/paradigma/conduct.html ) .
119+ By contributing to this project you agree to abide by its terms.
0 commit comments