4 ms·
I use careers.stackoverflow.com as a portfolio and am pretty happy with it; but it does suffer from the lack of functionality that you point out (it mostly aggr
by MalcolmDiggs 12y ago
I use careers.stackoverflow.com as a portfolio and am pretty happy with it; but it does suffer from the lack of functionality that you point out (it mostly aggregates and links to data).
The issue I have in general is that most people just wanna see pretty websites in your portfolio; which (as a server-side guy) is increasingly outside of my domain. Linking to a github instead of live-projects solves this except that:
1. Most my github repos are private (and so invisible to most visitors unless I invite them to the project)
2. There's no good way to highlight certain files/directories in github. There's no way to say "I wrote this class over here, and these unit tests over there, and all these controllers, so check those out".
I would love a portfolio tool that solved both issues: Allow me to pull highlights from private and public repos that show off key elements that I'm proud of (and if it's a private repo, don't give access to anything I didn't explicitly highlight). Highlight it in a beautiful/graphical way, allow me to comment in it and guide the viewer through a tour of code, of sorts. That kind of tool would be amazeballs.
- dennybritz 12y agoGreat feedback, thank you.
- lifeisstillgood 12y agoThat's a good idea - and sounds a lot like ... Documentation. Or possibly "Literate Profiles" I don't mean that crassly, just I think that Sphinx is close to that, and could just get tipped over the edge if we try hard. I like the idea and it should be doable with a few tweaks to something like Sphinx.
- MalcolmDiggs 12y agoGood points, but I was thinking of something more curated and streamlined than documentation. Perhaps Sphinx meets Bespoke.js (http://markdalgleish.com/projects/bespoke.js/ http://markdalgleish.com/projects/bespoke.js/)
- lifeisstillgood 12y agoGlossing over the private repo issue for a moment, and bein totally GitHub centric 1. Have each repo contain a 'presentation.rst' file, and they have simple format - header, '.. literalinclude' directives (done right) and commentary. Other highlights can be comments on issues, comments on pull requests etc 2. The presentation is formed in js/doco style with two columns - code on one, commentary on another. 3. Timelines that show where the literalinclude was committed, and along which are the other highlights in some rollover form 4. The whole timeline is created from all the presentation.rat files in all the listed repos. 5. Why not link in blog posts as highlights too? Any URL could easily be linked, with a commentary This is looking fun
- MalcolmDiggs 12y agoVery nice, and I love how it's github-centric (and you could incorporate it into your workflow). OP: whaddya think? Is this trending in the direction you were thinking?
- dennybritz 12y agoYep, this is great. I'm drafting up some specs now :)