Replies: 2 comments
-
|
For research-style projects, the cleanest GitHub setup is usually one repo per project with a consistent structure—keep notes, code, and the final report together, but clearly separated by folders. It makes the work reproducible and easy for others to review. Recommended structure (single project repo): README.md → 5–10 lines: problem, data sources, method, key results + screenshots + how to run report/ → final PDF + figures notebooks/ → EDA + analysis notebooks (numbered in order) src/ → reusable functions / pipelines data/ → sample or small data only (use data_raw/ ignored by git, or links to storage) dashboard/ → app code (Streamlit/Dash/etc.) + Dockerfile (optional) requirements.txt / environment.yml + LICENSE When to split into multiple repos Only if the dashboard becomes a standalone product (separate deploy cycle), or you want a shared library used across projects. Best practices that impress reviewers Add a one-page summary in the README (charts + findings) Include a reproducible pipeline (Makefile / scripts) and clear setup steps Use GitHub Releases for “final report v1.0” Use GitHub Pages (or a /docs folder) if you want the report to look like a mini-site If you want, tell me your tech stack (Python/R? Streamlit? Tableau?) and I’ll tailor the folder layout. |
Beta Was this translation helpful? Give feedback.
-
|
We made the decision to disable the ability to earn Achievements in our Community in order to discourage users from participating in coordinated or inauthentic activity like rapid questions and answers in order to earn badges. You can learn more about this decision in our announcement post here Achievements will no longer be available in the Community. Note that GitHub's Acceptable Use Policies prohibits coordinated or inauthentic activity like rapid questions and answers. As a result, we'll be unmarking the answer and locking this post. Any future violations may result in a temporary or indefinite block from the Community. Thanks for understanding. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Body
Hi GitHub Community,
I’m a Finance student building research-based projects (on-chain analytics, crypto research, dashboards).
What’s the best way to structure repositories for:
Research reports
Data analysis notebooks
Dashboard projects
Should I separate:
Research notes
Code
Final reports
Or combine them into a single structured repo?
Any best practice examples would be appreciated.
Beta Was this translation helpful? Give feedback.
All reactions