Advertisement
Guest User

Untitled

a guest
May 14th, 2019
80
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.45 KB | None | 0 0
  1. Method 1: code everything for your thread within the middle 300px of the post box
  2.  
  3. Pros:
  4.  
  5. - you can position things (using margins) with px with little worry mobile will fuck it up
  6. - what you see on your desktop/laptop is what (most) people will see on their phones
  7.  
  8. Cons:
  9.  
  10. - a looot of wasted space on the desktop/laptop version of the thread but it looks perfect on mobile
  11. - tiny threads, basically, and it's not recommended for word heavy threads either
  12.  
  13. Method 2: do not define a width for your outer span and then code the inner spans relative to the outer span
  14.  
  15. Pros:
  16.  
  17. - things resize on their own and you don't have to worry too much about mobile responsiveness
  18. - probably the easiest of the three methods and the one I use the most when coding
  19.  
  20. Cons:
  21.  
  22. - you (usually) end up having to do a lot of span layering to make this work, which can get confusing fast
  23. - not recommended for certain types of designs such as those using multiple columns (they get shrunken a lot)
  24.  
  25. Method 3: code using vw and vh as your units or code with percentages as your units
  26.  
  27. Pros:
  28.  
  29. - probably the most optimal way to get the code to match across platforms since it's based on screen size
  30. - things typically position the way you'd expect them to, so it's good for simple designs
  31.  
  32. Cons:
  33.  
  34. - resizing can fuck up complicated designs (it's just a confusing thing to me)
  35. - it is also super annoying to use half of these units (vw/vh) but percentages aren't /as/ bad
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement