We are working to build great features for the Women Who Code community and we want to highlight that work with our stakeholders, you! THANK YOU to our contributors for dedicating their free time to help us build tech a place where women can excel.
You can follow all of our work on github. Below are a few snippets of our awesome features.
We've been working hard this week on a host of incredible upgrades and features for our products. First up, we've been focused on improving our customer's experience when using the job board. This includes an automated system to notify them when their posts get published to the CODE Review, a redesigned posting interface to make contact messaging options more clear, an updated FAQ with images more clearly outlining the posting process, tracking for every link on the job board, as well as a design update that hides the schedules tab on the user nav when it is not applicable to that user. We also built in an option to show when certain plan levels are sold out.
On Network pages we changed the word
launched to better align with the organizations philosophical outlook, and updated the top nav buttons so that they remain consistent across all zoom levels. We've also started building a referral system that will better show us where users came from when they visit WomenWhoCode.com.
In addition we've been working to improve the overall performance of the website by removing duplicate resources and top level cache's.
Now we have a CONTRIBUTING to more accurately communicate our guidelines and workflow.
Our repo is private, yet running under an open source license. Instead of pointing to issues and PRs, we are including a screenshot of what our weekly pulse looks like.
Existing website contributors, please check out our pulse!
Potential website contributors, please email email@example.com with your github username to get started. It's built in Ruby on Rails + React + Postgresql.
Continuing to improve the stability and function of our platform so that we can do amazing things throughout the year.
If you accidentally blow away code changes in a later commit, use git reflog to go back in time to when your changes were around.
To submit feedback, comments or questions email firstname.lastname@example.org, we would love to hear from you.