Open jeffworley opened 8 years ago
jeffworley.github.io journal-week-6 PR: https://github.com/jeffworley/jeffworley.github.io/pull/32
tiy-assignments reading-etsy-api PR: https://github.com/jeffworley/tiy-assignments/pull/39
jeffworley:feature--product-page-add-to-cart to TIY-Durham:release--0.0.0--yak-shaving PR: https://github.com/TIY-Durham/TIY-Catalog/pull/25
jeffworley:category-page-side-filter-form to TIY-Durham:release--0.0.0--yak-shaving PR: https://github.com/TIY-Durham/TIY-Catalog/pull/26
Issues on the class TIY-Catalog Repo: https://github.com/TIY-Durham/TIY-Catalog/issues/3 https://github.com/TIY-Durham/TIY-Catalog/issues/4
USERNAME.github.io
:journal-week-6
intomaster
release--*
intomaster
feature--*
intorelease--*
TIY-GitHub
:release--*
intomaster
feature--responsive-yaks
intorelease--*
feature--*
intorelease--*
TIY-Catalog
:feature/planning-*
intoTIY-Durham:develop
TIY-Durham:develop
intodevelop
USERNAME.github.io
journal-week-6
release--*
feature--*
TIY-GitHub
release--*
frommaster
feature--responsive-yaks
fromrelease--*
feature--*
fromrelease--*
TIY-Catalog
feature/planning-*
fromdevelop
USERNAME.github.io:journal-week-6
_posts/
TIY-GitHub:release--*
specs/
-- what's different?TIY-Catalog:feature/planning-*
specs/
-- Skitch your features!specs/
!24 -- Shave and Let Die
And the Beat Goes On
You know the drill by now, don't ya? 1 reflective journal, 1 tutorial journal, 1 resource (bookmark) journal in a branch of your
USERNAME.github.io
repo calledjournal-week-6
... which should be frommaster
with a PR back intomaster
. Since you've now got such a nice place to put all those_posts/
, why not put 'em there?Reminder about format:
If you're linking your Resource Journal to the top-level page of some API documentation, you're doing it wrong. Drill down to a specific piece of the documentation instead and explain why and when it's useful.
If you have more than 5 steps, your Tutorial Journal might be too long for our time constraints. Try splitting it up into a series of posts that you can continue working on and put any additional ideas in your parking lot for later.
BEAST MODE
Bet you've still got some work on that awesome template, don't you? Why not start working on another incremental release in the meantime? Maybe just a tiny feature?
Reading APIs: Etsy
As you can tell, we'll be working with the Etsy API documentation this week to build out our catalog. Prepare yourself to answer the following questions about the API; more coming tomorrow!
Shaping Up with Angular JS
Throughout the week, you'll be assigned a piece of Shaping Up with Angular JS on CodeShool to work through. For tonight, play through the entire course by watching the videos and just taking the answers on the challenge. Type them yourself -- quickly -- to move forward. Take a screenshot of your badge for the course when you complete and attach it to your WIP Issue.
From GitHub With Love
Last week you built out your GitHub profile and realized... Github doesn't use breakpoints. There are no Media Queries whatsoever. Use the Devive Inspector in Chrome Dev Tools to switch your User-Agent (UA) identifier to a mobile device and reload into a whole new world. That's adaptive rather than responsive, and that's a problem.
Let's fix it!
Your solo assignment for the week is to make your GitHub profile responsive by adding Media Queries... and a little invention. Tonight, document the modifications you'll need to make in your
specs/
folder. Cut a newrelease--*
branch frommaster
and a new branch from that calledfeature--responsive-yaks
for this work.BEAST MODE
If you're looking for trouble, maybe you should clean up that GitHub profile a little in some additional feature branches? Remember, use as little markup as you need and pick classes and tags that convey meaning.
Planning is Important!
This week we're going to build a couple of pages from Etsy.com, and that means we need some yaks shaved! Fork the class project and then clone your fork locally. Pick a feature from our User Story list and claim it in the Slack channel. Convert it to an Issue in the main repo and assign it to yourself. Could use some more details... Maybe a checklist...
Create a feature called
feature/planning-YOUR-FEATURE
, whereYOUR-FEATURE
is the name of your feature, of course. Skitch some screenshots of your feature inspecs/
and open a PR back toTIY-Durham:develop
.Logistically, you'll be working in 3-person teams this week. Form teams yourselves, but run them by us for approval. Try to work with folks that you haven't already worked with.
We should start with the "Trending" page but quickly explore a single "Product Detail" page. Etsy also lists products that match a search result and curates their own "Featured Collections". Let's see how far we can get!
Install-fest!
We've got new tools this week -- GulpJS and a host of plugins. You should already have installed GulpJS globally, but if not, go ahead and do so. No need to assign them as dependencies yet... we'll do that together.