<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog on Huy Minh Ha</title><link>https://minhhh.github.io/categories/blog/</link><description>Recent content in Blog on Huy Minh Ha</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sat, 10 Sep 2016 00:00:00 +0700</lastBuildDate><atom:link href="https://minhhh.github.io/categories/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>Setup Github pages as your blog</title><link>https://minhhh.github.io/posts/setup-github-page-as-your-blog/</link><pubDate>Sat, 10 Sep 2016 00:00:00 +0700</pubDate><guid>https://minhhh.github.io/posts/setup-github-page-as-your-blog/</guid><description>&lt;p&gt;How to setup github page as your blog? It&amp;rsquo;s actually very easy, just follow the following guides&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a class="link" href="http://24ways.org/2013/get-started-with-github-pages/" target="_blank" rel="noopener"
 &gt;Get Started With GitHub Pages (Plus Bonus Jekyll)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class="link" href="http://www.thinkful.com/learn/a-guide-to-using-github-pages/start/new-project/user-page/" target="_blank" rel="noopener"
 &gt;A guide to using Github Pages&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class="link" href="http://knightlab.northwestern.edu/2013/06/13/getting-github-why-journalists-should-know-and-use-the-social-coding-site/" target="_blank" rel="noopener"
 &gt;Getting GitHub: Why journalists should know and use the social coding site&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class="link" href="https://github.com/csswizardry/csswizardry.github.com" target="_blank" rel="noopener"
 &gt;csswizardry.github.com&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>What is Medium</title><link>https://minhhh.github.io/posts/medium/</link><pubDate>Thu, 03 Dec 2015 00:00:00 +0700</pubDate><guid>https://minhhh.github.io/posts/medium/</guid><description>&lt;p&gt;Medium is a web-based service that let anyone publish articles online that was founded in 2012 by 2 founders of Twitter: Ev Williams and Biz Stone. Ev Williams said Medium was &amp;ldquo;a new place on the Internet where people share ideas and stories that are longer than 140 characters and not just for friends.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;According to wikipedia, medium is a &lt;a class="link" href="https://en.wikipedia.org/wiki/Medium_%28publishing_platform%29" target="_blank" rel="noopener"
 &gt;blog publishing platform&lt;/a&gt;. While Medium might look like a standard blogging platform, it had been &amp;ldquo;designed for little stories that make your day better and manifestos that change the world.&amp;rdquo; And yet &amp;ldquo;it helps you find the right audience for whatever you have to say.&amp;rdquo;. Also, Medium does not show articles in a reverse-chronological index of content like normal blogging platform.&lt;/p&gt;
&lt;p&gt;Medium seems to do following:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Create a beautiful, simple blogging platform for everyone&lt;/li&gt;
&lt;li&gt;Pay some people to post to the site, but not most of them&lt;/li&gt;
&lt;li&gt;Promote the people they&amp;rsquo;ve paid along with a very small subset of everyone else.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Therefore the content on medium can be either be:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;awesome if they were written by profesisonal writers who were hired and edited by professional editors&lt;/li&gt;
&lt;li&gt;opposite of awesome if they were written by mediocre bloggers.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The differences between Medium and traditional publication are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;If the traditional publication publish anything bad or plagiarised, it reflects poorly on them.&lt;/li&gt;
&lt;li&gt;If Medium publishes anything bad or plagiarised, it reflects poorly on the writers&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Medium is good for you if:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;You aren’t not going to blog a lot.&lt;/li&gt;
&lt;li&gt;You like the Medium environment.&lt;/li&gt;
&lt;li&gt;You aren’t in it for the money. Medium does have some paid contributors, but not for everyone.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="references"&gt;REFERENCES
&lt;/h2&gt;&lt;ul&gt;
&lt;li&gt;&lt;a class="link" href="http://www.theatlantic.com/technology/archive/2013/08/what-is-medium/278965/" target="_blank" rel="noopener"
 &gt;What is medium&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class="link" href="http://time.com/37586/what-is-medium-medium-is-pretty-cool-thats-what/" target="_blank" rel="noopener"
 &gt;http://time.com/37586/what-is-medium-medium-is-pretty-cool-thats-what/&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Embed git file to pelican</title><link>https://minhhh.github.io/posts/embed-git-pelican/</link><pubDate>Thu, 11 Sep 2014 00:00:00 +0700</pubDate><guid>https://minhhh.github.io/posts/embed-git-pelican/</guid><description>&lt;p&gt;Writing articles in github pages is nice, because you have github repository with all the nice features for document management, however sometimes it&amp;rsquo;s not where I want my articles to reside. For instance, I want the articles about git to be in a separate &lt;code&gt;git&lt;/code&gt; repository.&lt;/p&gt;
&lt;p&gt;I have several solutions for this problem:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;I could duplicate the article. But I won&amp;rsquo;t do this.&lt;/li&gt;
&lt;li&gt;I could store the articles as &lt;code&gt;gist&lt;/code&gt; like this:&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;[gist:id=dc8b7c536d0fe9c7003f]&lt;/p&gt;
&lt;p&gt;But I can&amp;rsquo;t store a lot of related things in gist because that&amp;rsquo;s the role of a real git repo.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;I could store the articles in the normal &lt;code&gt;git&lt;/code&gt; repo, and embed it into the article in github page. I chose this approach for long articles. Like this:&lt;/li&gt;
&lt;/ul&gt;
&lt;!-- &lt;script src="http://gistit-minhhh.appspot.com/github/robertkrimen/gist-it-example/blob/master/example.js"&gt;&lt;/script&gt; --&gt;
&lt;p&gt;There&amp;rsquo;s already a nice tool to do this: &lt;a class="link" href="https://github.com/minhhh/gist-it" target="_blank" rel="noopener"
 &gt;gist-it&lt;/a&gt;. Using it is really simple, just clone the repo and deploy it to an AppEngine instance. The downside of this is it does not generate &lt;code&gt;html&lt;/code&gt; code for &lt;code&gt;Markdown&lt;/code&gt;.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The best solution for me is to use a plugin for embedding git file into &lt;code&gt;pelican&lt;/code&gt; like this:&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a class="link" href="https://github.com/minhhh/wiki" target="_blank" rel="noopener"
 &gt;minhhh/wiki/sample.md&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Creating this blog</title><link>https://minhhh.github.io/posts/creating-this-blog/</link><pubDate>Sat, 07 Jun 2014 00:00:00 +0700</pubDate><guid>https://minhhh.github.io/posts/creating-this-blog/</guid><description>&lt;p&gt;When creating this blog, I used the following references:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a class="link" href="http://ntanjerome.org/blog/how-to-setup-github-user-page-with-pelican" target="_blank" rel="noopener"
 &gt;Setup github page with pelican&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class="link" href="http://mathamy.com/migrating-to-github-pages-using-pelican.html" target="_blank" rel="noopener"
 &gt;Migrating to github pages&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class="link" href="http://www.macdrifter.com/2012/08/pelican-guide-moving-from-wordpress-and-initial-setup.html" target="_blank" rel="noopener"
 &gt;Pelican Guide initial setup&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class="link" href="http://www.macdrifter.com/2012/08/moving-to-pelican-design-planning.html" target="_blank" rel="noopener"
 &gt;Moving to Pelican planning&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class="link" href="https://github.com/streeter/pelican-gist" target="_blank" rel="noopener"
 &gt;pelican-gist&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class="link" href="https://github.com/minhhh/gist-it" target="_blank" rel="noopener"
 &gt;gist-it&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</description></item></channel></rss>