Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Weekend Assignment - Oct 31st - 2nd - Proposed Plan of Attack #321

Open
44 tasks
AriGonzo opened this issue Oct 30, 2014 · 3 comments
Open
44 tasks

Weekend Assignment - Oct 31st - 2nd - Proposed Plan of Attack #321

AriGonzo opened this issue Oct 30, 2014 · 3 comments

Comments

@AriGonzo
Copy link

Responsive Product Grid Layout

  • Responsiveness
    • Mobile-First
    • Tablet
    • Desktop
  • Functionality
    • Onclick shirt flip
    • Onclick shirt flip-back
  • HTML blocking/layout
    • Skitch the site
  • CSS Styling/Transitions
    • Creating a 'style guide' with:
      • colors
      • hover effects
      • fonts
        • family
        • weight
        • size
      • line thickness/weight/height
      • icons or fancier icons or WHATEVER ELSE YOU FIND!!!
  • Source Placeholder images
  • Make pixel perfect

Horizontal Slide Out Menu

  • Responsiveness
    • Mobile-First
    • Tablet
    • Desktop
  • Functionality
    • Drop down
    • slide up
    • transition show/hide
    • close all menus when selecting last two options
  • HTML blocking/layout
    • Skitch the site
  • CSS Styling/Transitions
    • Creating a 'style guide' with:
      • colors
      • hover effects
      • fonts
        • family
        • weight
        • size
      • line thickness/weight/height
      • icons or fancier icons or WHATEVER ELSE YOU FIND!!!
  • Source Placeholder images
  • Make pixel perfect
@fab9
Copy link
Member

fab9 commented Oct 30, 2014

Regarding responsiveness... there's 3 breakpoints listed (mobile-first, tablet and desktop). The original has 5 breakpoints though.

@mema82
Copy link

mema82 commented Oct 30, 2014

Are we adding this checklist to our own issue and checking off or just updating ONE person to manage this particular issue?

@AriGonzo
Copy link
Author

@fab9 Once we get together tomorrow, we can make some decisions as a group about where we want the breakpoints to be. This is a living document and I expect to make a ton of changes to this to adapt to our plan.

@mema82 I'm thinking that we should just have the one document. @phillycc and I can act as project managers and update this document as we check things off the list, but as we're working as a team, we can keep it all centrally located here. If there's anyhting that needs to change on this doc, let me know and I'll make the change/check things off.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants