Where the design community meets.
Make this a microsite :)
Love it! I've always used ugly cheat sheets for this. This is nicely organized.
Or simply just a good Product Designer...
If anyone is interested! This is a great post by Julie Zhuo (Director of Design) which outlines what we generally look for and the process designers go through. http://firstround.com/review/An-Inside-Look-at-Facebooks-Method-for-Hiring-Designers/
The reset is used to remove all of the default stylings which browsers add, if you look at a page without applying any css you will notice that certain html tags still render with styles, for example h1 tags will render the text larger. Usually in the most simple form you'll use resets to control padding/margin inconsistencies.
Here's a great read i'd recommend if you're interested in learning more : http://sixrevisions.com/css/should-you-reset-your-css/
So simple answer to your question is build it from scratch. All of the options i'll point out below require knowledge in html,css and proper static site structures and honestly all they provide is simple organization and set-up. Making static websites is easy to do manually without any of these. A CMS like Squarespace would allow you to do these things without learning how to code.
A lot of people mention Jekyll. Personally I find it too restrictive but it is good if you'd like your site to display and organize itself around a blog structure. If you want something a bit more flexible something like http://cactusformac.com/ let's you work around templates you create and the structure is up to you. Cactus uses django and offers easy set up with pre processors like sass etc.
What a typical 'troll'-reply
I think this is an excellent idea. I would also even go as far as to contact the website creators and get a small summary of their approach towards constructing the site itself and their challenges.
Minor notes, mostly visual:
Extending screenshots outside of the canvas looks pretty bad when you put this into code and a user goes past your generous 1300px canvas width. Also why hide valuable UI? You want to show them what they're diving into.
Phrasing your titles into questions forces the user to read more because you aren't directly stating the solution. Personally I find this pretty annoying, I would love to see the results you receive towards this approach as most landing pages propose the solution straight up.
Iconography next to the titles aren't very contextual atm and are kinda confusing in general. Also those widows are very apparent.
Drop shadow on the green buttons are a little muddy, i would suggest just not having them, would increase contrast on white.
I would think about consolidating the Twitter feedback breaks into maybe one section towards the end, or a constantly rotating feed. Right now they don't do much but distract you from learning about the product.
"Quick Left" section before the footer seems inappropriate and confusing. The focus should primarily be about the product. What you have in the footer seems enough.
Idk if just having the ">>" at the end of text links is enough to distinguish that it's a link especially since you use bold blue text in other areas?
I personally prefer seeing portfolios like this now and days, especially when the person is more in a product oriented role. It's becoming increasingly more important to show your thought process and involvement in projects rather than just designs as many designers vary is range of actual involvement.
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.