21 Jul 2016
Reading time ~2 minutes
What I Did
- Intern Project Group Stand-up
- Intern Class: Accessibility
- Client Side Apps Meeting
- Paired with Eli to clarify deployment concerns and implementation of some of the last remaining features of the site.
- Built out the Ruby classes corresponding with defined CK components. Data inputted through the CMS currently renders onto the homepage for “These Numbers Matter”. As far as bare build out is concerned, my work here is officially done. However, there is much fun to be had in the form of refactoring, automated testing, and correcting bugs detected from manual QA.
What I Learned
- From the Accessibility meeting: Accessibility for web pages is not meant to solely target individuals with visual, physical, motor, cognitive, and seizure disorders or impediments. Rather, there is a whole range of impediments that all people face which fall within a spectrum of permanence and situational applicability. In other words, making websites accessible benefits all people, and web dev shops ought to take it more seriously on a whole.
- From the client app meeting:
- Web sockets are really cool if you know how to manipulate them.
- Omniscient is a REACT library providing an abstraction for React components that allows for fast top-down rendering embracing immutable data for js.
- The process for contributing to coveted open source projects is a lot easier than one might expect, so get on it!
- Heroku uses dynamic IP’s so one ought to supply one’s DNS provider “somename.herokuapp.com” as the CNAME or ALIAS record, allowing for the purchased domain name to point to the desired Heroku server.
What I’d Like to Learn
Though I’ve familiarized myself with a single instance of explicit meta-programming within the
component.rb class that Eli handed over to me in which
has_attribute methods were being generated for a given attribute within a given CK component class, I should really venture deeper into the world of meta-programming and its merits particularly within Rails.