We are building 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 valuable 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.
This week, the Women Who Code Core Team made an exciting update that unites our Job Board with our newly launched Track Communities. We also implemented a number of minor but important fixes across the site, to improve display visibility and the function of our features.
Job Section on Network Profile
Sometimes jobs are posted with locations that are not near local Networks. However, we recently launched WWCode's Track Community program, which allows Women Who Code members around the world to take part in remote learning opportunities with our new team of Fellows. This update ensures that jobs which are relevant to the subject of a certain Track, now show up on that Track's page.
Responsive Blog Hero
We had an issue where we had set a static height for blog heros, which were cutting off long blog titles. This was caused by shared hero styles across the website. We solved the problem by consolidating all hero styles into a single file, updating the styles, creating shared BlogPost category react components to ensure consistent styles across the website, and reorganizing the BlogPosts React Components into new folders.
Strip out @ so deep links work on ApplaudHer Twitter
When an ApplaiudHer with an @ Twitter social link is clicked, in a Chrome browser, the Twitter app will now show the user's WWCode profile.
Handle Elasticsearch timeouts/errors
We fixed some minor timeout errors that were occurring with the site's search function on blogs, Networks, and jobs index pages.
Fix Missing Network in Network Event
You used to be able to submit a Network event without associating it with a Network, which would cause it to not show up on the Network page. We fixed this by installing a failsafe to ensure that the Network param exists before creating an event. If it does not, an error is returned to the user.
To submit feedback, comments or questions email email@example.com, we would love to hear from you.
Join our User Research Team! Be the first to check out all of the great products that we are building and have your voice heard from the earliest stages of development.