-
Notifications
You must be signed in to change notification settings - Fork 744
Feedback Guidelines
Our project is open source because we believe that improving mental health education and culture requires open dialogue. However, please keep in mind that our project is not solving all of the problems that exist in mental health treatment.
Our mission is to improve conversations about mental health experiences with loved ones, we are not looking to provide a medical or clinical service, which includes connecting our users to specific therapists or counselors.
There is a growing number of companies and projects that are doing this, some of which we showcase on our Resources page. That being said, we are very open to feedback (and have received it in the past) from mental health professionals. We want to mindful of language, attitudes, and behaviours that promote empathetic, compassionate, and supportive dialogues about mental health.
We recently went through a major redesign thanks to Nishiki Liu. We are open to minor updates to our logo and colours if they improve accessibility. Overall design changes must improve usability.
While we are always looking for ways to improve our tech stack and code quality, suggestions like, "You should use Python and Django" without stating any reasons why is not helpful. All software is legacy code and while you may not "love" our main tech stack (Ruby on Rails and React), we continue to use it because it has not blocked improvements from being made. If it does block us in the future, we will take the appropriate steps to make changes.
To address the occasional "You should use microservices" feedback we get, that is something we have discussed multiple times with respect to moving to a single-page app architecture. There is currently no plan to migrate to this architecture as we have other priorities.
Please send us feedback via GitHub or Google Forms for improving translations. Our translations are gender neutral and have a similar tone as talking to a loved one. We do not tolerate inappropriate or stigmatizing language.
Every post in our blog has met our guidelines. If you an encounter an issue with something you've seen on our blog, please email us at [email protected].