devdocs/specs/core-ui-design.txt

@@ -276,6 +276,8 @@ Plan: Layout and design each component for the smallest screen size first, then
     - It makes no sense to target individual devices anymore. Instead, add breakpoints where your design breaks. 
     If you start with your design for the smallest device and start to drag your browser window wider, when do the lines become too long to read comfortably? 
     When could you make better use of the screen? That is the point at which to add a Media Query and write some additional CSS.
+        - So design with the tiny ones and minimalist, then drag out and see where can add more value with more stuff.
+        - Ideally at this point I'd like to see small and large only, medium specific design not necessary but testing obviously is (TIME TO MARKET!)
     - NAV For example a menu can be fully shown as icons in a larger size but might be behind another click in smaller
     - Functionality: figure out what the minimum most important things to show at small size then add more "optional" stuff as it increases
         - Grid: show the Name column first and selector, then add the most relevant columns in order of relevancy
@@ -286,7 +288,3 @@ Plan: Layout and design each component for the smallest screen size first, then
 
 Can I make one component for each type that is responsive or do I need to make a separate component for each breakpoint I will support?
     - One component pros: less code to maintain theoretically, cons: maybe less well designed for that size
-
-todo: need to determine what breakpoints I'm going to support specifically
-    - todo: What are the most common device sizes I'll be dealing with?
-    - todo: once I have decided common device sizes then can figure out breakpoint plan