humancompanion / portfolio Goto Github PK

Capture the case study of this project for OMB.

Need to first determine what I can and cannot talk about.

I'm convinced that it is time for the hamburger menu to go: http://deep.design/the-hamburger-menu/

The right solution is to revise the header to include the 3 links necessary at any size. Start with a tab bar for narrow viewports and then expand into the menu I already have at wider viewports (with perhaps a location change to be under the header rather than on top).

That means ditching the contact card in the header and moving it down into the footer. That makes more sense anyway.

Use the latest picturefill (2.0) for images: https://github.com/scottjehl/picturefill

I may want to adjust the font-family and font-size for narrower/smaller screens. That was definitely the trend at one point though I/we got away from it later on. Some analysis revealed:

• Apple's Reader option switches serif to sans-serif for mobile ("FranklinITCProLight","HelveticaNeue","Helvetica Neue Light","Helvetica Neue",Helvetica,Arial,"Lucida Grande",sans-serif;). That's a non-free font btw. They seems to retain the size and line-height of the original css.
• Vox doesn't switch but, they use a large base size and line-height (20px/32px) throughout.
• NY Times uses 16/23px Georgia throughout in wider viewports and 18/28px in narrower viewports.
• A List Apart switches from 18/26px to 24/36px at 600px (37.5em).

I need to do some more research to refresh my memory on the argument for going with a smaller font size on mobile (which seems counterintuitive).

• Initial draft
• Revise framework/outline
• Add "Nod to WPA" RE: landing page
• Add "What we did" component
• Add a separate federal hiring story with callout that opens a new page

Outline

A. How we framed the project

• Build from the strength of the App Guide
• Trail from outside or landing > Search > Job announcement > Apply
• Immersive exposure

B. What we did

• Dashboard
• Landing - WPA
• Search
• Auth
• Profile

C. North Star & USDS Pilot

• Brief summary of both and how they are different
• Include screenshots of the pilot JOA
• Eventually link to the Pilot Playbook
• Add note about being able to walk through the report in person

I should show that I have some expertise in creating cards by creating a contact card in the header.

This would get back to where I was with the XML version of my resume which allowed for converting to different formats (HTML, PDF, and text).

https://jsonresume.org/

This is more complicated than it should be. Here are the options:

1. Use the master branch for dev and gh-pages branch for "production" and then have a different header in gh-pages that would be included.
   • This requires includes via Jekyll, Assemble, or grunt-include-replace.
2. Switch to the minified version everywhere and rely on grunt to update it after every change.
   • If change were calming down this might work but, unlikely.
3. Use grunt-usemin
   • This plugin has a problem with relative paths that requires changing the directory structure: http://stackoverflow.com/questions/18964875/how-should-i-configure-grunt-usemin-to-work-with-relative-path