WW<CODE> Maker Bytes
Written by WWCode Core Team
Issue 162
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.
Released
The Women Who Code Core Team has been hard at work making several critical updates to the site's core programming including upgrades to the react-rails gem, fixing a Rspec error, and adding a way to keep track of resizing breakpoints using React. We've also been working on an admin dashboard feature to make it easier to update the About Page as our team grows, and added an Opportunities page that features scholarships, free tickets, and other ways to boost your career.
Added
Context and theme
We need to be able to dynamically keep track of the current breakpoint that we are currently at as we resize the window of the app without passing it down as props. This is where React context can help. Once we are able to create breakpoint information within context we need to keep track of the breakpoints in a theme.js
Add link to static page /opportunities
– A link to the "Opportunities" page was added to the footer of the website. This page contains information about scholarships, free ticket giveaways and calls for papers.
Create team_members table and admin UI
– We are working on a function that will let website admins update the About page on the website from the backend interface. This is important as Women Who Code has been growing exponentially over the past few months with multiple team members being added as we expand our mission to inspire women to excel in technology careers.
Create Accessible Radio Button Component
– We added a new accessible global radio component for the Edit Profile form.
Changed
Upgrading react-rails gem to 2.3.1
In this PR we stair-stepped versions of our gem up to 2.3.1, which included:
– Adding new server rendering requirements
– Minor syntax updates
– Deleting any unnecessary references to key props (it's bad form and caused an error in the console, now)
– Removing all references to React.CreateClass and replacing it with extends React.Component
– Making inputs be controlled if console errors occur (ex: value is controlled by state)
– Checking against null values for inputs (due to console errors)
Fixed
Rspec alert fix
The following alert message was being displayed in the console whenever the ResourcesController#search method ran in a spec file or in the browser: "The body option replaces the entire body, so the following options are ignored: page, per_page." This was caused by the first set of pagination params (page and per_page) that were being passed to searchkick, outside of the body of the custom query handled by elasticsearch. Solution: Since we can't override searchkick's pagination defaults (because it causes the alert message we're trying to fix), we're manually calculating the next_page value using the per_page limit we've defined for Resources.
Applauds!
Talk to us
Any ideas about existing features, new features, getting involved as a contributor, please share it in this FORM and/or watch our repos on Github.
To submit feedback, comments or questions email coreteam@womenwhocode.com, we would love to hear from you.
User Research is a Team Sport
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.