BJO (Kindle Publishing Files)
ArchivedMarch 1, 2020
A repo where Kindle Direct Publishing files were stored — probably not the wisest archival strategy, but a practical one at the time. A deep look at how Kindle Create makes book publishing accessible to anyone, and the honest tradeoffs between self-publishing, agencies, and traditional publishing.
Purpose
Used this repo to store KDP manuscript files. In hindsight, a Git repo is not the best archive for publication-ready PDFs and formatted manuscripts — a cloud drive or dedicated asset management system is more appropriate. But the content it points to is real: multiple published books, and a working knowledge of the self-publishing pipeline.
Stack
What I Learned
- Kindle Create is Amazon's free formatting tool that takes a Word doc or PDF and converts it into a properly formatted Kindle eBook or print-ready interior. It handles page breaks, chapter headings, table of contents, and print margins. The output is a .kpf file that uploads directly to KDP. For a solo publisher, it eliminates the need for InDesign or professional formatting for simple books.
- The KDP publishing flow is: write the manuscript, format it (Kindle Create or manual), design the cover (or use KDP's Cover Creator for a basic one), fill out metadata (title, subtitle, author, description, categories, keywords), set pricing and royalty options (35% or 70% depending on price point and territory), and publish. The book is live on Amazon within 72 hours. No gatekeeper. No query letters. No rejection.
- Print-on-demand through KDP means zero inventory risk. When someone orders a paperback, Amazon prints a single copy and ships it. You never hold stock, never manage fulfillment, never eat the cost of unsold books. The tradeoff is per-unit cost — a POD paperback costs more to produce than a bulk offset print run, so your margin per book is thinner. But for low-volume or experimental titles, POD is unbeatable.
- Amazon's algorithm favors books with strong metadata: specific categories (not broad ones), relevant keywords in the title and subtitle, a compelling description with HTML formatting, and consistent review velocity. Understanding KDP as a search engine changes how you approach publishing — you are optimizing for discoverability, not just writing a good book.
- Storing publication files in a Git repo works technically but is wrong architecturally. Git is designed for text files with frequent small changes — diffs, branches, merges. Binary files like PDFs and .kpf exports do not diff well, bloat the repo, and cannot be meaningfully merged. The right tool: Google Drive, Dropbox, or a dedicated DAM (digital asset management) system with version history.
Key Insights
- Self-publishing through KDP is the Firebase of the book world — it removes the barrier between "I wrote a thing" and "anyone on Earth can buy it." The tradeoff is the same as Firebase: you gain speed and autonomy, you lose curation, marketing support, and the prestige signal of being traditionally published. For most first-time authors, especially those publishing niche or experimental content (like 101 Potato Haikus), self-publishing is the correct choice.
- Traditional publishing (the Big Five: Penguin Random House, HarperCollins, Simon & Schuster, Hachette, Macmillan) offers advances, professional editing, cover design, distribution to physical bookstores, and cultural legitimacy. The cost: you give up creative control, royalties are 10-15% of list price, the process takes 1-2 years from acceptance to shelf, and most manuscripts are rejected. For literary fiction and mainstream nonfiction, this path still makes sense. For everything else, it is slow and gatekept.
- Agencies and hybrid publishers sit in the middle. A literary agent shops your manuscript to traditional publishers and takes 15% of your advance and royalties — they are incentivized to get you the best deal. Hybrid publishers charge the author upfront for professional editing, design, and distribution, blurring the line between service provider and vanity press. Some are legitimate (high production quality, genuine distribution). Many are not. Due diligence is mandatory.
- The honest comparison: self-publishing gives you 35-70% royalties, full creative control, and instant time-to-market, but you handle editing, design, and marketing yourself. Traditional publishing gives you professional polish and bookstore distribution, but you wait years and keep pennies on the dollar. The right path depends on your goal — building a brand (self-publish) vs. winning a Pulitzer (go traditional). For Potato Literature, self-publishing is the clear answer.
This post was composed through a conversation between Brett Owers and Claude Code (Anthropic). The content reflects Brett's recollection of each project and the lessons drawn from it. Some details may be approximate or omitted — the purpose is to paint an honest picture of a software engineer's development over time, not to serve as a precise historical record.