Mkd => json

[meandavejustice]

Haven't had much experience testing stream-modules like this.. I would really like some guidance, structuring that.

Last test is currently failing.

We would eventually like to set up a travis like thang to make sure that speaker files match the template correctly before merging.

Here is a sample of the JSON output. Here is a sample of the JSON output. (really wish there was pretty print support here)

{"name":"Forrest Lehwalder Norvell","avatar":"![not a brony](https://0.gravatar.com/avatar/44c00253ab6c0e681820c82e9a2264d1?r=x&s=200)","attributes":{"location":"San Francisco, CA, US","twitter":"@othiym23","github":"othiym23","urls":["urls"],"travel-availability":"if comp'd","preferred-audience-size":"whatever"},"About me":{"body":"Node is a great platform but it can be scary to get started with, and it can\ncontinue to be scary to plumb its depths. I'm comfortable with Node's (and\nJavaScript's) many idiosyncracies and awkward design tradeoffs and really enjoy\nhelping other people get more comfortable as well. Having done all of free-form\ntalks with questions, formal presentations, and hands-on workshops, I enjoy all\nthree, although I do better when there are frequent opportunities for\nquestions."},"Talks / Workshops":{},"Domains: your friends and neighbors":{"location":"NodeConf 2013","when":"2013-06","materials":"http://othiym23.github.io/nodeconf2013-domains/#/","duration":"8 x 60m","audience-size":"~40 attendees per session","body":"I spent at least 1 second coming up with a title for my deck."},"Thinking asynchronously":{"location":"RealtimeConf 2013","when":"2013-10","materials":"http://www.slideshare.net/othiym23/rtc-2013","duration":"12m","audience-size":"large","body":"A distillation of a talk I delivered to my colleagues at New Relic about the\nimportance of modeling data flow asynchronously, and the implications of\nasynchronous data modeling.  It was kind of an esoteric topic and it is\nsomething I continue to think about and refine, but it's a subject that's near\nand dear to my heart."},"Beyond the MEAN stack":{"location":"Node Summit 2013","when":"2013-12","materials":"http://www.slideshare.net/othiym23/beyond-the-mean-stack-thinking-small-with-nodejs-for-the-enterprise","duration":"20m","audience-size":"medium","body":"Aimed more at technical managers and people choosing the tools to be used for\nnew projects than core developers, this talk attempted to show the breadth of\nthe Node ecosystem as a means of showing that to standardize on an \"optimal\nstack\" was to negate a lot of the advantage of choosing Node in the first\nplace. The audience feedback was positive and Eran Hammer told me he thought my\njokes were funny, which made me happy."},"process":"Forrest Lehwalder Norvell\n![not a brony](https://0.gravatar.com/avatar/44c00253ab6c0e681820c82e9a2264d1?r=x&s=200)\n\nAbout me\nI'm a Node engineer for New Relic who has contributed significantly to their\ninstrumentation for Node.js. I've been using Node professionally since 2011,\nco-ran one of the session tracks at NodeConf 2013, and have contributed some\nsmall pieces to Node core. My most significant public project aside from\n[node-newrelic](https://github.com/newrelic/node-newrelic) is probably\n[continuation-local storage](https://github.com/othiym23/node-continuation-local-storage),\nof which I am the primary maintainer. No server-side JavaScript is too gross\nfor me to be interested in.\nNode is a great platform but it can be scary to get started with, and it can\ncontinue to be scary to plumb its depths. I'm comfortable with Node's (and\nJavaScript's) many idiosyncracies and awkward design tradeoffs and really enjoy\nhelping other people get more comfortable as well. Having done all of free-form\ntalks with questions, formal presentations, and hands-on workshops, I enjoy all\nthree, although I do better when there are frequent opportunities for\nquestions.\nTalks / Workshops\nDomains: your friends and neighbors\n\nDomenic Denicola and I co-presented a hands-on workshop on Node's domains. I\nspecifically pitched this session to Mikeal Rogers because I felt that domains\nwere underused but quite powerful. The sessions were very well-received and\nI've continued to get feedback and field questions about domains ever since. I\nalso reviewed the material for a PDXNode meeting. It was a ton of work, but I\nthink I learned as much as the attendees and it left me with a lasting fondness\nfor hands-on workshops.\nI spent at least 1 second coming up with a title for my deck.\nThinking asynchronously\n\nA distillation of a talk I delivered to my colleagues at New Relic about the\nimportance of modeling data flow asynchronously, and the implications of\nasynchronous data modeling.  It was kind of an esoteric topic and it is\nsomething I continue to think about and refine, but it's a subject that's near\nand dear to my heart.\nBeyond the MEAN stack\n\nAimed more at technical managers and people choosing the tools to be used for\nnew projects than core developers, this talk attempted to show the breadth of\nthe Node ecosystem as a means of showing that to standardize on an \"optimal\nstack\" was to negate a lot of the advantage of choosing Node in the first\nplace. The audience feedback was positive and Eran Hammer told me he thought my\njokes were funny, which made me happy."}
]

If you would like to check out the output locally in a readable way you can run node index.js | python -mjson.tool

[hackygolucky]

WHOA!!!!!! \o/

On Thu, Feb 20, 2014 at 1:05 PM, Dave Justice [email protected]:

---

You can merge this Pull Request by running

git pull https://github.com/meandavejustice/speakers mkd-json

Or view, comment on, or merge it at:

#6
Commit Summary

• mkd-json first run
• Merge pull request Word-smithing :) #1 from meandavejustice/mkd-json
• parsing json to mkd
• Merge branch 'master' into mkd-json
• Merge branch 'master' of github.com:knode/speakers
• Merge branch 'master' into mkd-json

File Changes

• A index.js https://github.com/knode/speakers/pull/6/files#diff-0(78)
• A lib/mk.js https://github.com/knode/speakers/pull/6/files#diff-1(97)
• A package.jsonhttps://github.com/Mkd => json #6/files#diff-2(34)
• M portland-or-usa/justin-abrahms.mdhttps://github.com/Mkd => json #6/files#diff-3(16)
• A portland-or-usa/your-name.mdhttps://github.com/Mkd => json #6/files#diff-4(42)
• A test/index.jshttps://github.com/Mkd => json #6/files#diff-5(12)

Patch Links:

• https://github.com/knode/speakers/pull/6.patch
• https://github.com/knode/speakers/pull/6.diff

Reply to this email directly or view it on GitHubhttps://github.com//pull/6
.