EDITORCLASSBLOGLOGINOpkleOpkle, the Editor for CreatorsInfiniteExpression,In New Forms.New ContentOpkle makes an editor so anyone can build for the web without code, and share it anywhere.Blending text and screen, we build tools that make the web about imagination, not code.Keeping Your Own Voice in the Age of AIai11How to Revise Professionally with AIai12Ethics and Responsibility in Professional AI Writingai13Building a Professional AI Writing Workflowai14Building Opkle Editor: Where Writers Stop at EPUBdev189101112...1 Building Opkle Editor: Where Writers Stop at EPUB

I didn't start building Opkle Editor out of some grand market analysis. I had worked as a full-stack developer at an IT platform company and then an AI company before striking out on my own, and all along I was also someone who writes and makes books. I have published two books myself, and I have taken part in a number of book fairs, where I met the people who make books up close. One scene from those fairs stayed with me for an odd length of time. Creators weren't struggling because they couldn't write. They already had their stories, and they were already thinking about covers, sentences and readers. Yet they often stalled at the moment of turning that manuscript into an ebook.

At first it puzzled me. As a developer, EPUB was not an unfamiliar format. If you know HTML and CSS you can understand the structure, and anyone who has worked with web documents can see why the text reflows, why a table of contents appears, and why styles are kept separate. But to the authors I met at book fairs, EPUB was less a free publishing format than a “difficult, complicated file that throws errors.” That gap kept nagging at me.

EPUB is not an expressively weak format by nature. It is built on HTML and CSS, the same roots as web documents. It can reflow to fit the screen size and the reader's settings, and it can carry links, images, fonts and even accessibility information. Forms of expression that differ from print are entirely possible. In actual production, though, those possibilities were hard to see. What creators ran into first was not possibility but tags, folders, CSS and validation errors.

What I Heard at Book Fairs

At a book fair you meet the people who made books from very close up. Someone has bound a season of their life into a book, someone has woven drawings and photographs into a small publication, someone has turned sentences they held onto for years into a single physical object. For them a book is not simply a product. It is the way a thought they have carried for a long time travels over to the reader.

But even when they had managed to make a print book or a PDF somehow, the mood often changed once EPUB ebooks came up. I kept hearing things like “I'd like to make an ebook too, but it's too hard,” “I don't know where to start,” and “They say validation shows errors, but I don't understand what that means.” People with enough content of their own to make a book became beginners again, standing in front of an unfamiliar technology.

The more I listened, the stranger it felt. EPUB is a format that could open up more possibilities for creators, yet to creators it was arriving as a new burden rather than a new freedom. The ability to make a book and the ability to handle code were bound together far too tightly. It was a structure that suddenly demanded HTML, CSS, packaging and validation from people who write, choose images and imagine how readers will move through a text.

The Distance I Felt Looking at Sigil

There were, and still are, widely used tools for making EPUBs. Sigil is the best known of them. It is undeniably an important tool, and it lets you open and edit EPUB files directly. For someone who knows HTML and CSS it is powerful. The problem was that many of the creators I met at book fairs found it hard to make their own books that way.

To my eyes, Sigil often looked like “a code editor for handling the EPUB folder structure.” If you want to fix a heading you have to look at tags, if you want to adjust a margin you have to know CSS, and to check whether the file is valid you have to go through yet another validation tool. That may be a natural procedure for a developer, but for an author it meant the flow of making a book kept being interrupted.

Error checking was especially like this. W3C validation and accessibility checks are essential for the quality of an ebook. For an EPUB to be distributed, to open reliably in many readers and to reach more people, these steps are unavoidable. But the sentence “there are errors” alone gives a creator nothing to move forward with. What is wrong and why, how to fix it, and what that fix means for the book's reading experience all had to be connected.

From then on I came to think that the tooling problem was not simply a matter of having more or fewer features. Creators are not people who want to avoid technology. They are people who want to meet the technology their book needs in the language of their own work. EPUB tools, though, still felt like they were looking at creators from the developer's seat.

Easy in Code, Hard in Practice

As a developer, understanding the structure of EPUB was relatively clear-cut. There are set files inside a compressed archive, the body text is made of HTML, and styles are organized in CSS. There is a table of contents and metadata, and images and fonts go in alongside. Technically, that is how you can sum it up.

A creator's work doesn't organize itself that way. Authors make books out of feelings like “I'd like this paragraph to look a little quieter,” “I'd like this image to breathe between the lines,” “I'd like readers to turn this scene slowly.” A developer translates that into tags and styles, but there is no reason an author should have to think that way from the start.

That difference loomed larger and larger for me. It wasn't enough for a tool that makes EPUBs simply to show the file structure well. The process of seeing, touching, fixing and checking their own book had to feel natural to the creator. If making ebooks stayed purely a coding task, EPUB would remain a format that only some people could handle properly.

That was when a question took shape in my mind. Without knowing HTML and CSS, could creators work directly on the structure and design of their own books? Could error and accessibility checks be brought inside the process of finishing a book, instead of being a separate, frightening procedure? Could making an ebook become a creator's workflow rather than a developer's task?

The Moment I Decided to Build an Editor

What I wanted to build was not just a program that saves EPUB files more easily. I wanted an editor where creators can directly handle the structure and design of their own books, understand what a result means without knowing HTML or CSS, and check errors and accessibility problems within the flow of their work. I didn't want to force creators to learn a code editor. I needed a tool that lets them work with EPUB in a creator's own language.

My first resolve was simple: I hoped every author could express themselves through EPUB. By “every author” I don't mean that everyone should make books in the same way. Quite the opposite. I meant that text-centered books, image-heavy books, books that need movement, books that sit somewhere between teaching material and literature, every kind of content should be able to come alive in an ebook in its own way.

Good software isn't finished just by packing in features. You have to know at what moments users get stuck, what they fear, and which decisions they want to make themselves. For an EPUB editor, that meant asking not only “is the file valid?” but also “does this book read the way its creator intended?”

That is how the development of Opkle Editor began. It didn't begin as a repackaging of existing technology, but as a way to reduce, one by one, the blockages creators actually hit when making books. The first goal was not some sweeping automation. It was to keep authors from stopping in front of their own books because of technology, and to bring the expressive freedom EPUB holds a little closer to creators' hands. That was why I decided to build this editor.

PreviousListNext
CopyrightAll design outputs and videos on this website are copyrighted by Abstract Cloud and protected under copyright law and related regulations. All content, including web, video, text, cover, and interior designs, is the property of the copyright holder. Unauthorized reproduction, distribution, creation of derivative works, or online sharing without prior consent is strictly prohibited. Violations may result in civil and criminal liability under copyright law. Legitimate purchases and copyright protection preserve creators' rights and fuel better works in return.Copyright: Abstract Cloud | CEO: Bae Changkyu
© Abstract Cloud. All Rights Reserved.
HOMEFAQTerms of ServicePrivacy PolicyRefund PolicySeller Informationhelp@opkle.app
+82 10-2747-3403
Business Name :Abstract Cloud  |  CEO :Bae ChangkyuBusiness Registration Number :249-74-00533E-commerce Registration Number :2025-Uijeongbu Songsan-0634Address :402, 108-dong, 49 Buyong-ro, Uijeongbu-si, Gyeonggi-do, Republic of KoreaAll content, designs, and source code on this website
are copyrighted by Opkle.
Opkle