Ok, so I've gone back on my no-images approach to this. One big reason was aesthetics, but the other reason was realizing that I'd need to double the code to create the arrow on the right side as well, and that just becomes more work than its worth.
I'm realizing slowly that just because something can be done in CSS, doesn't mean it should be done in CSS.
^ Agreed. Very much enjoyed reading your thoughts and development on this shot + the previous one and definitely think you've come to a good conclusion.
3 Responses
Pro
Pat Dryburgh
Ok, so I've gone back on my no-images approach to this. One big reason was aesthetics, but the other reason was realizing that I'd need to double the code to create the arrow on the right side as well, and that just becomes more work than its worth.
I'm realizing slowly that just because something can be done in CSS, doesn't mean it should be done in CSS.
7 months ago
Good decision. One has to be pragmatic: it looks better, it's going to be easier to manage & your code will be easier to read.
7 months ago
Pro
Claire Coullon
^ Agreed. Very much enjoyed reading your thoughts and development on this shot + the previous one and definitely think you've come to a good conclusion.
7 months ago