This article is about a man, a machine and a thousand lines of code. Scratch that, it’s about an idea. This is how things begin. You got an idea, you work on it — there’s nothing else. My idea started way back in 2007 when I created a WordPress theme to relieve the pain of bad designed templates people had to deal with.
Basically, all I wanted is for you to write on the web just like you write on a notebook and read what you’ve written just like you read a book. Input should be easy, output should be beautiful. Are you getting it? Easy input, beautiful output.
My marriage with code started in November last year when I joined a local startup. This is how I learned Django, getting up there and working with the best. Then things come from themselves, using Sass, thinking about doing an alternative to Bootstrap, playing with PostgreSQL, design for interaction first, mobile at the core of the product, models, queries, views, templates and all other stuff that comes in and out of a Git repository.
Fail Before You Start
Markdawn will fail before it will even start. I know this very well. Because I’m not the best developer in the world, because nobody wants to use yet another platform, because the name is plain wrong and doesn’t make sense, because very few people know about markdown or even using it to write their documents or articles.
Knowing all this stuff, I still think I should try. Why? Well, these are the top six features of Markdawn:
- Easy to read — mobile first experience
- Easy to write — fluid interface that adapts to the big screen
- Ranking — stories promoted by number of comments
- Social networking at the core
- Markdown documents storage in the cloud
- Designed by one of the best UX designers
Now you know why I have written I’m Stuck with Writing, because I was busy creating Markdawn — a new way to write digitally. I hope this won’t be the last article here, since I’ll continue to write on my Markdawn space from now on.