pushkin-consortium / pushkin

A customizable, scalable ecosystem for massive online psychological experiments
https://pushkin-consortium.github.io/pushkin/
MIT License
24 stars 10 forks source link

Add overview to new monorepo to "Developer" section of docs #319

Open jkhartshorne opened 3 months ago

jkhartshorne commented 3 months ago

Something that explains (or points to a tutorial on) changesets, etc.

Basically, if somebody had never seen a monorepo, didn't know about changesets, etc., what would they need to read to make sense of things.

Asking for a friend. :)

jkhartshorne commented 3 months ago

@jessestorbeck -- maybe assign this to someone?

jessestorbeck commented 3 months ago

Some of this is covered in the contributions section, but a "repo orientation" section might be nice too and have some additional information, e.g. Q: "What does pyproject.toml do?"; A: "We use the Python package manager Poetry in conjunction with MkDocs to build our documentation; pyproject.toml tells Poetry how to set up the build environment for the docs."

@hunterschep @ayang21 -- This seems natural to include in Getting started on development. Maybe as the second #-level heading?

jessestorbeck commented 2 months ago

I've take a stab at this in 67d101579d479df7fc1cbb2793bdf3802cb53420. It's folded into working on the linting setup though, so not currently ready for a PR. It looks like this though:

Screenshot 2024-04-09 at 6 31 05 PM

And with the annotation expanded:

Screenshot 2024-04-09 at 6 31 17 PM

I went back and forth about what was the best way to format it. I tried a diagram with Mermaid (like the contribution flowchart) and that was terrible. Annotations seemed like the best way not to overwhelm the page with text.