/
atom.xml
103 lines (87 loc) · 5.1 KB
/
atom.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
<title><![CDATA[Category: blogging | sudo random]]></title>
<link href="http://rajatkhanduja.com/techblog/categories/blogging/atom.xml" rel="self"/>
<link href="http://rajatkhanduja.com/"/>
<updated>2014-06-18T11:25:16+05:30</updated>
<id>http://rajatkhanduja.com/</id>
<author>
<name><![CDATA[Rajat Khanduja]]></name>
</author>
<generator uri="http://octopress.org/">Octopress</generator>
<entry>
<title type="html"><![CDATA[Why Octopress?]]></title>
<link href="http://rajatkhanduja.com/techblog/2014/03/11/all-set-and-ready-to-go/"/>
<updated>2014-03-11T23:00:37+05:30</updated>
<id>http://rajatkhanduja.com/techblog/2014/03/11/all-set-and-ready-to-go</id>
<content type="html"><![CDATA[<p>Finally, the site is up and ready! Now, all that remains is for me to make all
this effort worthwhile and start blogging regularly. </p>
<p>The experience of setting up this blog, however, taught me a lot of things. Not
just the lessons required to setup <a href="http://octopress.org">Octopress</a> or this
particular theme (<a href="https://github.com/shashankmehta/greyshade/">Greyshade</a>) or
the DNS, but …. oh, who am I kidding, that’s the set of things I gained out of
this entire experience. But they are not really worth sharing, except probably
the incident where I ended up with an infinite loop of URL redirection because
of an error in configuring the DNS! </p>
<p>So, this post will be less about the hows, but whys! Why did I choose Octopress
(and Greyshade) and why do I expect this to be a good choice? That’s the question
I will focus on. </p>
<!--more-->
<ol>
<li>
<p><strong>Blogging right from my editor</strong></p>
<p>While this might not make much sense to a lot of people, it means a lot to
some of us to be able to do most of the things from within our favorite editor.
Being a <a href="http://vim.org">vim</a> fan myself, it gives me immense pleasure to be
able to write this blog from the editor. The fools who’d argue that one could
just copy the content from one’s editor for blogging doesn’t know the importance
of formatting, hyperlinking, etc. in blogging. It becomes all the more important
when you aim to write blogs that would tend to include code snippets. Like
Latex, I could write most of the content first and worry about the
formatting later. That brings me to the next point …</p>
</li>
<li>
<p><strong>Not having to worry about formatting</strong></p>
<p>I quite perfectly fit the stereotype of developers who lack any sense about
the UI/UX. Many a times <a href="http://vickychijwani.github.io">Vicky</a> has laughed
off at the interface I found ‘usable’. In such a case, it only makes it harder
for me to imagine how the out put of my blog should look like. What Octopress
(or most such tools) offer, like Latex, is that most of the formatting
decisions are taken care of without asking me. For instance, I needn’t worry
about the size of the heading or the color of the <a> tags. Should
it look green on hover or yellow? I needn’t worry about that. While at the same
time, I get the ability to tinker parts that I do need fixed or changed. This
might be probably a good example of
<a href="https://en.wikipedia.org/wiki/The_Paradox_of_Choice%3A_Why_More_Is_Less">Paradox of Choice</a>.
I don’t have to think about making responsive UI, or the alignment of text
or the margin-width, which saves me from making a lot of decisions and I
feel less tense! </p>
<p>Having tried some platforms prior to this, I know that most platforms don’t
offer smooth writing/formatting tools. My experience with
<a href="http://blogger.com">Blogger</a> was quite troublesome when I kept running into
issues with the blockquote tag and had to resolve it by looking into the
HTML itself. <a href="http://wordpress.org">Wordpress</a> and <a href="http://medium.com">Medium</a>
seemed to provide great formatting tools for general blogging, but none
that had good support for technical blogs right out of the box. Sure, there
are plugins and being a geek I could have found them, but it only convinces
me that they were not made for technical content.</p>
<p>Moreover, being a vim fan, I enjoy tools that focus on commands/instructions
based on ‘typed commands’ rather than key combinations. vim’s support
for markdown only makes it easier for me to be sure of getting what I expect.</p>
</li>
<li>
<p><strong>Writing in offline mode</strong></p>
<p>While this might be more of a perk that I expect to use over time, this is
barely something I have required as of now. Since the setup doesn’t require
a special server to interpret the content, I can preview and/or save a draft
whenever I want. Only to deploy do I need access to the Internet. However,
as I am connected most of the time, this might not be as useful.</p>
</li>
</ol>
<p>Anyway, this is me just getting started with this platform and resuming blogging
after a long time. Maybe I’d have a lot of changes to these initial thoughts,
maybe not.</p>
<p>Cheers!</p>
]]></content>
</entry>
</feed>