Live data from Hacker News

Show HN: ReadMe.io – Beautiful Documentation Made Easy

readme.io

21–30 of 82 posts

Re: Show HN: ReadMe.io – Beautiful Documentation Made Easy

#21
"ReadMe has made our lives infinitely easier. We've had it on our todo list for over a year, and a day after finding ReadMe we had our docs launched. We're super impressed. You guys have built a fucking awesome tool."

I don't know, but having swearing on a professional website is probably not the best way to go. Looks like a nice startup though.

Re: Show HN: ReadMe.io – Beautiful Documentation Made Easy

#22
post #18

Earlier quoted context omitted.

[deleted]

This came up when we were working on this, the team at ReadMe has been very responsive about this and I don't feel like we'll be trapped on the platform. They use Markdown for almost everything except some widgets, and since I'm going to use mainly Markdown I don't feel locked in. I also feel confident that if I kindly asked for the contents of my site, the team at ReadMe would send it on over in what ever way they c…

Sorry about that. I thought it sounded negative and didn't want to talk badly about the product.

My question was basically "Are you okay with publishing content on a site that owns the content?"

I imagine they are building export tools in the future, and this is just the first version.

Re: Show HN: ReadMe.io – Beautiful Documentation Made Easy

#23
We just released our API on apiary (http://docs.commando.apiary.io), but after finding ReadMe.io on ProductHunt, we signed up for a paid plan that very day, and are in the process of migrating over.

Our focus for our API documentation is beautifully designed and easy to read. All the extra features of Apiary and Mashup such as proxying, rate limiting, billing, and mocking requests are not really a priority for us. ReadMe.io is a perfect fit.

Re: Show HN: ReadMe.io – Beautiful Documentation Made Easy

#26

We just released our API on apiary ( http://docs.commando.apiary.io ), but after finding ReadMe.io on ProductHunt, we signed up for a paid plan that very day, and are in the process of migrating over. Our focus for our API documentation is beautifully designed and easy to read. All the extra features of Apiary and Mashup such as proxying, rate limiting, billing, and mocking requests are not really a priority for us.…

What made you decide to get a paid plan instead of the free plan?

Re: Show HN: ReadMe.io – Beautiful Documentation Made Easy

#27

"ReadMe has made our lives infinitely easier. We've had it on our todo list for over a year, and a day after finding ReadMe we had our docs launched. We're super impressed. You guys have built a fucking awesome tool." I don't know, but having swearing on a professional website is probably not the best way to go. Looks like a nice startup though.

to be fair the people who get appalled by reading the f-word are probably not the target customer. who drops f-word all the time? programmers, entrepreneurs, designers, developers, managers. certainly not established 100 year old corporation, but most certainly the hip, fast moving, horny, 20~30 something olds who eat and breathe technology.

Re: Show HN: ReadMe.io – Beautiful Documentation Made Easy

#28

"ReadMe has made our lives infinitely easier. We've had it on our todo list for over a year, and a day after finding ReadMe we had our docs launched. We're super impressed. You guys have built a fucking awesome tool." I don't know, but having swearing on a professional website is probably not the best way to go. Looks like a nice startup though.

I'm not in any way opposed to vulgarity in general, but I have to admit that this stuck out to me too. Not really necessary.

(Though my first thought wasn't "Who puts 'fucking' in their testimonials section," it was "Who puts 'fucking' in a business email to a new vendor?")

Re: Show HN: ReadMe.io – Beautiful Documentation Made Easy

#30

The code blocks are really something else in terms of looks. Is that a custom look, or is it some open source plugin?

Custom! We spent a ton of time on the "documentation builder", since we wanted it to be as painless as possible to write documentation.
Post reply on HN