Using My World History Book: A Practical Walkthrough
I use My World History Book fairly regularly for mapping out chronological content, and it works well enough if you understand how it handles data entry. The basic setup is straightforward. You create a topic, add events with dates, and arrange them into chapters or modules. Most people who approach this tool expect it to behave like a traditional authoring platform, but it has some quirks that become apparent quickly. Start by defining your subject area. The platform asks for a title, a brief description, and a target audience level. After that, you begin adding events. Each event takes a date, a title, and a description block. That sounds simple enough, but the date formatting catches most people off guard. The system expects ISO 8601 format. If you type something like "July 14, 1789" instead of "1789-07-14", it will either reject the entry or misinterpret it, and the timeline renders out of order. This took me about twenty minutes to figure out on my first project, which covered the French Revolution. I wasted a morning because I hadn't read the format spec before starting. Once your events are in, you can group them into chapters or modules. The grouping is flexible. You can nest chapters within chapters if your content demands it, or keep everything flat. For a standard course or overview book, a two-level hierarchy works fine. Anything deeper gets messy in the export.
Exporting and Sharing Your Content
The export feature is where the tool becomes genuinely useful, and also where it shows its limits. You can generate PDFs, EPUB files, or HTML bundles. The PDF output is clean and readable, but it does not handle wide tables well. If your events include columns for region, significance rating, or primary sources, the table columns will compress or overlap depending on your page orientation. I learned this the hard way when exporting a chapter on the Silk Road. The table had five columns, and the resulting PDF made the text inside the cells nearly illegible at standard zoom. The workaround was to rotate those specific pages to landscape after export, which the built-in tool supports, or to split the table across two pages manually in the editor before exporting. The EPUB export is more flexible for mobile reading but requires additional formatting in the source editor. If you want images to display properly in EPUB, you need to embed them directly rather than linking externally. External links break in offline readers, which defeats the purpose of exporting to EPUB in the first place. I switched to embedding all images locally a while back, and it added maybe ten minutes of prep time per chapter but saved me from having to re-export three times.
Common Pitfalls and What They Cost You
The biggest issue I have found is version conflicts when multiple people edit the same project. The platform allows collaborative editing, but it does not handle simultaneous edits gracefully. If two users modify different events at the same time, both changes save without conflict resolution. This means you can end up with partial overwrites where one person's additions disappear. I have lost entire sections of content this way. The fix is to lock the project during editing sessions, which is a manual process you have to coordinate with whoever else is working on it. Set a shared calendar or use a simple chat thread to communicate editing windows. It adds friction, but it prevents data loss. Another thing worth mentioning is the search function. It indexes event titles and descriptions, but it does not index chapter headings or user-added tags unless those tags are placed inside the description body. This is a small detail that matters a lot once your project grows past about fifty events. Searching for "Treaty of Westphalia" will find it, but searching for "European" as a thematic tag will not surface events tagged that way unless the word appears in the description text. I ended up adding a line to every event description that includes the relevant thematic keywords, which is redundant but necessary given how the search currently works.
Get the Full Details
When My World History Book Is the Right Choice
This tool makes sense for educators and independent writers who need to produce structured chronological content without investing in a full Learning Management System. It is not designed for heavy multimedia projects or courses that require quizzes, graded assignments, or progress tracking. If you need those features, you should look at platforms like Teachable or Thinkific instead. My World History Book sits in a narrower lane: it is for people who want to write and format history content cleanly and export it for distribution. The pricing model is subscription-based, and the free tier has generous limits for individual projects. If you are producing content for a classroom or a small audience, the free tier covers most needs. Paid plans unlock unlimited projects and priority export queues, which matters more if you are under a tight deadline. The export queue on the free tier can take up to twenty-four hours during peak usage, which caught me off guard once when I had a publishing deadline two days away. I upgraded to paid for that project alone, and it was worth it to avoid the bottleneck.
Final Notes on Workflow
The most efficient workflow I have settled on is to draft all event descriptions in a separate document first, verify the dates in ISO format, then bulk-import everything into the platform rather than entering events one by one. The import feature accepts CSV files, and it cuts the setup time for a fifty-event chapter from roughly forty minutes down to about eight. The catch is that the CSV template is strict. Extra columns get ignored, missing required fields cause silent failures, and you have to match the header row exactly. I keep a master template file with all the correct headers, and I fill that in before importing. It is a small habit that saves a significant amount of debugging time.
