Little Wonder

2025 · Public personal product

I built Little Wonder to help a child turn ideas and drawings into an illustrated storybook, with a cover and a printable PDF.

My role
Creator and engineer
Period
2025–2026
Status
Public personal product
Little Wonder storybook generator landing screen with a child character and floating creative tools
Little Wonder · A storybook workspace for a child’s ideas and drawings.
Project briefPERSONAL PRODUCT

Make the child the hero, not the prompt engineer.

I built Little Wonder around a child’s wish to make stories. It turns classic public-domain tales into personalised illustrated books with the child as the hero. The book includes a custom cover and comic-style pages, and can be downloaded as a print-ready PDF from the browser.

I wanted the choices to feel familiar to a child. Behind those choices, the software has to coordinate the text and illustrations while keeping the character recognisable from page to page. That consistency is a much more useful test than the quality of any single image.

The workflow behind the book

The visible interaction is deliberately small. A child chooses a story direction and supplies the details that make the book theirs. The application then has to coordinate several stages without turning the child into a prompt engineer.

  1. Story choice and child details
  2. Page-level story structure
  3. Character and scene illustrations
  4. Consistency review across pages
  5. Cover, layout, and printable PDF
The book workflow, from a story choice to a printable sequence.

Each stage has a different failure mode. A coherent story can still produce a different-looking hero on every page. Good illustrations can still fail when text and image compete in the layout. A browser preview can look correct while a printable PDF clips content or changes pagination.

The hard part was continuity

The test was not whether the system could generate one attractive image. The child needed to recognise themselves as the same hero throughout the book. That meant carrying identity, clothing, visual style, and page context across several independent generations.

I treated the book as a sequence rather than a gallery. Every page had to contribute to the same story, and the cover and PDF needed to feel like the output of that sequence rather than separate exports.

Keeping the interface child-sized

The application hides most generation detail. The useful choices are story choices: who the hero is, what kind of adventure they want, and which drawings or ideas they want to include. Model settings and production stages belong behind the interaction unless something needs the parent’s attention.

That constraint made Little Wonder a useful product exercise. The system does several technical things, but the person using it should feel that they are making a book.

Go deeper

Sources and links