| Thank you for your brutal honesty, I really appreciate it. Regarding some your points: 2. How's the layout broken? I'm on Firefox on Windows XP as well, and regarding fonts, this was one of the few Google fonts that actually rendered nicely on my screens in different browsers. Some are utter crap, I really thought I had found one that isn't. Maybe specifying absolute font sizes would fix things. 5. Ouch. Although I'm not sure the layout is completely broken, the graphics could use some more TLC. The 'full stack' image is supposed to convey some mosaic-like design (with the shades of grey) instead of a 'clean' version, but I'm aware a failed miserably in this regard. Will redo the image. 7. No problem. > I am left with the impression of a Jack of all trades but master of none. I prefer to think of myself as a specializing generalist, see http://www.agilemodeling.com/essays/generalizingSpecialists.... > you don't necessarily have much depth behind any of the technologies I figured the industry experience covered some of this > You're a UX designer, but your CV isn't optimised for scannability at all. Well, I've played the role of UX designer, not the same thing. I focused more on story-telling than scannability here, good suggestion though. > you're using a static background image .. instead of gracefully degrading CSS3
> you've failed basic cross-browser compatibility
> polishing up my front-end skills to get the design into shape Good points, thanks. Please consider this version 0.1. > how to organise your content for the way real people are going to read that CV If by 'real people' you mean recruiters, that's not my primary target audience, I have an utterly boring, scannable MS-Word document for them if needed. Also, the page doubles as an 'about me' page for peterdevos.com and my resume, this may have been a bad decision to begin with. > rookie mistakes in the design and lack of scannability are letting you down right now Agree to some extent. That's what this 'Show HN' post was for, to get initial feedback. Again, thank you, much appreciated. |
I assume the layout breaks on my setup because I have set the default browser font size to 18px and you're using em's (which are relative to the base font) to define all your font sizes.
Using relative font sizing isn't necessarily bad, but you should make sure that the whole layout is flexible enough. For example, you have set a static pixel height for the speech bubble and "full stack" containers. With a slightly different font setup that can cause the text to overflow (as can be seen in the screenshot above).
Great work this far, I'll bet you can make this a lot better by reading all the feedback in these comments.