Skip to main content

Contributing

Charles River is meant to improve through classroom use. Students and instructors often notice where a case needs a clearer walkthrough, where a report needs better explanation, or where a new exercise would make the material more useful. You do not need to write code to contribute. Short questions, plain-language suggestions, and classroom feedback are all useful contributions.

Ways You Can Contribute​

  • suggest a clearer explanation for a report, process page, or analytics case
  • ask a question when something feels confusing or incomplete
  • recommend a new example, exercise, or teaching sequence
  • share classroom feedback about what students or instructors needed most
  • point out a concrete mistake such as a typo, broken link, or incorrect reference

Start a Discussion​

GitHub Discussions is the main place to contribute ideas, ask questions, and suggest improvements. If you want to recommend new content, ask for a clearer explanation, suggest a better exercise, or share feedback from teaching use, start there first.

Typical discussion topics include:

  • "Could this page include a shorter business-first explanation before the SQL?"
  • "Can you add a payroll-focused exercise for students?"
  • "I am not sure how this report connects to the process flow."
  • "This case would be easier to teach with a recommended reading order."

GitHub Discussions

Start a discussion on GitHub

Choose the category that best fits your question, idea, suggestion, or teaching feedback. Short non-technical posts are completely fine.

Open GitHub Discussions

New to GitHub?​

You do not need to know GitHub well to contribute here:

  1. Open the Discussions link above.
  2. Pick the category that best matches your topic.
  3. Write your question, idea, or suggestion in plain language.

If you are not sure which category fits best, choose the closest one and explain what you are trying to improve. Maintainers can sort out the details later.

Report a Concrete Error​

Use GitHub Issues for a specific mistake that should be corrected, such as a typo, broken link, wrong query reference, factual error, figure problem, or missing report asset.

Report an Error in GitHub Issues

What Happens Next​

Maintainers read both discussions and issues. Discussions help shape new content, clarify confusing areas, and gather feedback from classroom use. Issues track concrete corrections. If a discussion becomes specific and ready to implement, maintainers may turn it into an issue and track the work there.

Notice a mistake?Report an error on this page