4 ms·

My solution for the last three or so years has been to maintain a personal site (http://www.steveasleep.com/ http://www.steveasleep.com/) that consists of these

My solution for the last three or so years has been to maintain a personal site (http://www.steveasleep.com/ http://www.steveasleep.com/) that consists of these things: * Links to and descriptions for relevant projects * List of recent blog posts (optional) * Latest 10 commits I have made to Github * HTML/PDF résumé * Links to my profiles on SO, HN, etc. As a college student casting about for internships, that simple combination has helped me a lot. If you're interested, I could help set you up with the super-simple backend that can be hosted for free on App Engine. I've also thought about adding a "hacker résumé" to supplement the regular one. The college job search format usually requires a conventional (boring) one-sheet résumé, but I would also like to provide a summary of hackerly accomplishments for the people I actually want reading my site.

techbio 16y ago
Sounds like a steady setup. How packagable is it? With AppEngine, you could make this an easier transfer by consuming a short list of URLs in a textarea (homepage, resume, blogA, blogB, profileA, profileB) and simply spawn a clone. Seen anything alse like it? I sort of asked here: http://news.ycombinator.com/item?id=1827294 http://news.ycombinator.com/item?id=1827294
- stevejohnson 16y ago
  Very packageable, actually. Here it is on Github: https://github.com/irskep/steveasleep https://github.com/irskep/steveasleep It reads the sidebar from content/site.yaml. Sidebar items can point either to external links or refer to Markdown files also in content/ which are converted to HTML at request time. The only other remaining customization is to change the theme in content/templates/. I like this instead of the feed-me-URLs setup because you can edit the Markdown and just hit Deploy in App Engine Launcher. Also, if I ever decide to move to App Engine, I have almost no barrier because I use the data store only for caching Posterous and Github information.

techbio 16y ago

Sounds like a steady setup. How packagable is it? With AppEngine, you could make this an easier transfer by consuming a short list of URLs in a textarea (homepage, resume, blogA, blogB, profileA, profileB) and simply spawn a clone. Seen anything alse like it? I sort of asked here: http://news.ycombinator.com/item?id=1827294 http://news.ycombinator.com/item?id=1827294

stevejohnson 16y ago
Very packageable, actually. Here it is on Github: https://github.com/irskep/steveasleep https://github.com/irskep/steveasleep It reads the sidebar from content/site.yaml. Sidebar items can point either to external links or refer to Markdown files also in content/ which are converted to HTML at request time. The only other remaining customization is to change the theme in content/templates/. I like this instead of the feed-me-URLs setup because you can edit the Markdown and just hit Deploy in App Engine Launcher. Also, if I ever decide to move to App Engine, I have almost no barrier because I use the data store only for caching Posterous and Github information.