Blurb gets two nods from the San Francisco Chronicle

Share the Blurb:
pin it button Blurb gets two nods from the San Francisco Chronicle

Our local newspaper ran a nice feature on Blurb in its technology section today and mentioned us in the Computing Q&A column, so we thought we’d share them both.

You’re a writer. Presto! A book.

“I wanted to create a photo essay book that looked like something you would buy at the bookstore, but who knew it would cost a jillion dollars and take several months?” Gittins, a former software executive, said in e-mail. “That just felt all wrong, so I started Blurb for all of us who have stories to tell, photos to share, and experiences to document.”

The writer, Dan Fost, helped edit his grandmother-in-law’s book, and used it as an example in the article. So, at 96, Sybil Plumlee is now a published author.

Plumlee’s book, “Stories of Hester Ann Bolin Harvey and Her Family,” meets that description. It’s a collection of family stories, including the tale of her grandmother’s trip across the Oregon Trail in 1850. (I’ll note that I’m biased, as the material is not only inherently interesting to me as a family member, but I also helped edit it.) It features an array of old photos and copies of pages from the family Bible, in which important birth and death dates have been hand-written for more than a century.

And then toward the end of the Computing Q&A column, Blurb gets another mention.

Q: I’ve created a family tree using genealogy software. Now I’d like to print it in the form of a book, complete with photos and images of family records such as birth certificates, all of which I have stored on my computer.

Is there software I could use to compile the book? And what’s the best way to get it printed (I would need about 25 copies to give away to other members of the family).

For the Chronicle’s answer, check out its Web site. Hint: The answer has something to do with Blurb.

Share the Blurb:
pin it button Blurb gets two nods from the San Francisco Chronicle

Post a Comment

Your email is never published nor shared. Required fields are marked *

(required)
(required, not published)

noshow