3 ms·

As someone that just finished an ebook[0] and went through making it a reality[1], I welcome the effort to make this step effortless. I don't think anyone reall

As someone that just finished an ebook[0] and went through making it a reality[1], I welcome the effort to make this step effortless. I don't think anyone really nailed this up until now. If you succeed, it could be huge! That said, I miss any kind of examples on the site. Let me see a finished ebook, let me try the editor. And because I am a technical writer, I have to ask. Will you support technical books? How will you handle code snippets, highlighting, or line comments? [0] https://deploymentfromscratch.com/ https://deploymentfromscratch.com/ [1] https://nts.strzibny.name/ruby-for-ebook-publishing/ https://nts.strzibny.name/ruby-for-ebook-publishing/

aswinmohanme 5y ago
Thanks for the support :D I really liked your detailed write up on the publishing chain you have used, code is just text in it's essence and because of that programmers have access to superior tools for it's manipulation. But that power is hidden behind a steep learning curve. IndiePaper is just the collection of tools you have specified all integrated and wrapped up as a web app. Regarding examples, I never thought this would blow up on HN, that's why it doesn't it even have an FAQ, I'm working on a new design that would bring published books of the platform front and center. Technical books are and will be supported, even though technical authors have the know-how to setup up a publishing toolchain, most would love to write in a completely integrated platform. Since we control the entire editor, we can and will support code snippets, highlighting and comments by adding to the text-editor raw structure and processing it during typesetting phase. IndiePaper was actually ideated with rich technical books from the start, features like code integration with Github were all thought of from the start. So IndiePaper will have first class support for technical books.

aswinmohanme 5y ago

Thanks for the support :D I really liked your detailed write up on the publishing chain you have used, code is just text in it's essence and because of that programmers have access to superior tools for it's manipulation. But that power is hidden behind a steep learning curve. IndiePaper is just the collection of tools you have specified all integrated and wrapped up as a web app. Regarding examples, I never thought this would blow up on HN, that's why it doesn't it even have an FAQ, I'm working on a new design that would bring published books of the platform front and center. Technical books are and will be supported, even though technical authors have the know-how to setup up a publishing toolchain, most would love to write in a completely integrated platform. Since we control the entire editor, we can and will support code snippets, highlighting and comments by adding to the text-editor raw structure and processing it during typesetting phase. IndiePaper was actually ideated with rich technical books from the start, features like code integration with Github were all thought of from the start. So IndiePaper will have first class support for technical books.